TransactionReceipt

TransactionReceipt

The summary of a transaction’s result so far. If the transaction has not reached consensus, this result will be necessarily incomplete.

Field	Type	Description
status	ResponseCodeEnum	The consensus status of the transaction; is UNKNOWN if consensus has not been reached, or if the associated transaction did not have a valid payer signature
accountID	AccountID	In the receipt of a CryptoCreate, the id of the newly created account
fileID	FileID	In the receipt of a FileCreate, the id of the newly created file
contractID	ContractID	In the receipt of a ContractCreate, the id of the newly created contract
exchangeRate	ExchangeRateSet	The exchange rates in effect when the transaction reached consensus
topicID	TopicID	In the receipt of a ConsensusCreateTopic, the id of the newly created topic.
topicSequenceNumber	uint64	In the receipt of a ConsensusSubmitMessage, the new sequence number of the topic that received the message
topicRunningHash	bytes	In the receipt of a ConsensusSubmitMessage, the new running hash of the topic that received the message. This 48-byte field is the output of a particular SHA-384 digest whose input data are determined by the value of the topicRunningHashVersion. Please see table below.
topicRunningHashVersion	uint64	In the receipt of a ConsensusSubmitMessage, the version of the SHA-384 digest used to update the running hash.
tokenID	TokenID	In the receipt of a CreateToken, the id of the newly created token
scheduleID	ScheduleID	In the receipt of a CreateSchedule, the id of the newly created Scheduled Entity
scheduledTransactionID	TransactionID	In the receipt of a ScheduleCreate or ScheduleSign that resolves to SUCCESS, the TransactionID that should be used to query for the receipt or record of the relevant scheduled transaction
serialNumbers	repeated int64	In the receipt of a TokenMint for tokens of type NON_FUNGIBLE_UNIQUE, the serial numbers of the newly created NFTs

Topic Running Hash

The input data to the SHA-384 digest in order.

topicRunningHashVersion	Input data to the SHA-384 digest in order
0 or 1	1. The previous running hash of the topic (48 bytes) 2. The topic's shard (8 bytes) 3. The topic's realm (8 bytes) 4. The topic's number (8 bytes) 5. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 6. The number of nanoseconds since 5. before the ConsensusSubmitMessage reached consensus (4 bytes) 7. The topicSequenceNumber from above (8 bytes) 8. The message bytes from the ConsensusSubmitMessage (variable).
2	1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The topic's shard (8 bytes) 4. The topic's realm (8 bytes) 5. The topic's number (8 bytes) 6. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 7. The number of nanoseconds since 6. before the ConsensusSubmitMessage reached consensus (4 bytes) 8. The topicSequenceNumber from above (8 bytes) 9. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes)
3	1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The payer account's shard (8 bytes) 4. The payer account's realm (8 bytes) 5. The payer account's number (8 bytes) 6. The topic's shard (8 bytes) 7. The topic's realm (8 bytes) 8. The topic's number (8 bytes) 9. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 10. The number of nanoseconds since 9. before the ConsensusSubmitMessage reached consensus (4 bytes) 11. The topicSequenceNumber from above (8 bytes) 12. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes)