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: 52721e10d4a93cfb6a3be9b3ab06670af6a486ea83c82d4ceadf568e4975bb68
Tx prefix hash: 3a7b8bd69ab3c5c52e670edea2d7750e1861b963cc2cdc05a351290a7f75805a
Tx public key: b113ed5d402e029c253fc295257d7e0aecec1f2a78c985057f8cb01f8fbc3943
| Timestamp: 1780981648 | Timestamp [UTC]: 2026-06-09 05:07:28 | Age [y:d:h:m:s]: 00:000:08:30:08 |
| Block: 8044 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 557 | RingCT/type: yes/0 |
| Extra: 01b113ed5d402e029c253fc295257d7e0aecec1f2a78c985057f8cb01f8fbc3943020900000001e49593ff00 | ||
1 output(s) for total of 34.648734049078 HMNY
| stealth address | amount | amount idx | tag |
| 00: bc259dc524c17cfa943b1ac523896762c434da3abcef334a7da226ce452b11b3 | 34.648734049078 | 9970 of 0 | <43> |
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": 8104,
"vin": [ {
"gen": {
"height": 8044
}
}
],
"vout": [ {
"amount": 34648734049078,
"target": {
"tagged_key": {
"key": "bc259dc524c17cfa943b1ac523896762c434da3abcef334a7da226ce452b11b3",
"view_tag": "43"
}
}
}
],
"extra": [ 1, 177, 19, 237, 93, 64, 46, 2, 156, 37, 63, 194, 149, 37, 125, 126, 10, 236, 236, 31, 42, 120, 201, 133, 5, 127, 140, 176, 31, 143, 188, 57, 67, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}