For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 56c34039eb0b8437653c8eecd97541cebd184beb9b268875fb3aa038d8f6624e
Tx prefix hash: 1071280d418739c6ce0931a9bd51f4f5a9f58e6cfad9bab0025865a5337e64b4
Tx public key: 3627676d3f6d4e91163260c059fcf9e98b675a65abf306d6c07c884181636273
| Timestamp: 1780122326 | Timestamp [UTC]: 2026-05-30 06:25:26 | Age [y:d:h:m:s]: 00:009:18:21:21 |
| Block: 4900 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2986 | RingCT/type: yes/0 |
| Extra: 013627676d3f6d4e91163260c059fcf9e98b675a65abf306d6c07c88418163627302090000000226697be300 | ||
1 output(s) for total of 34.857136693387 HMNY
| stealth address | amount | amount idx | tag |
| 00: dbf0d15d0c0e790e72d537d96955e78123958ceeda92a4fecb25c8c183963ebd | 34.857136693387 | 6209 of 0 | <b7> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 4960,
"vin": [ {
"gen": {
"height": 4900
}
}
],
"vout": [ {
"amount": 34857136693387,
"target": {
"tagged_key": {
"key": "dbf0d15d0c0e790e72d537d96955e78123958ceeda92a4fecb25c8c183963ebd",
"view_tag": "b7"
}
}
}
],
"extra": [ 1, 54, 39, 103, 109, 63, 109, 78, 145, 22, 50, 96, 192, 89, 252, 249, 233, 139, 103, 90, 101, 171, 243, 6, 214, 192, 124, 136, 65, 129, 99, 98, 115, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}