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: 0d9a4c42fa7f612c3f759ba07b51112ad8262130648946cbff9c59d37dfd53ba
Tx prefix hash: 8edc45cae817eb47addc6534fd0c23866de4f9e4565c62b2ef62f4e15ed8505f
Tx public key: f6528d84b8b8a50f1981c7004d85e17b1a4bfdcf5c7bfde84d9445c7a5420bbb
| Timestamp: 1780685854 | Timestamp [UTC]: 2026-06-05 18:57:34 | Age [y:d:h:m:s]: 00:003:02:14:33 |
| Block: 5403 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2483 | RingCT/type: yes/0 |
| Extra: 01f6528d84b8b8a50f1981c7004d85e17b1a4bfdcf5c7bfde84d9445c7a5420bbb020900000001e49593ff00 | ||
1 output(s) for total of 34.823710888228 HMNY
| stealth address | amount | amount idx | tag |
| 00: a0a04f1f191ea2f16240a995d0c23b7e6ffc81e8dd83cc511f7102bbe7227057 | 34.823710888228 | 6840 of 0 | <ec> |
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": 5463,
"vin": [ {
"gen": {
"height": 5403
}
}
],
"vout": [ {
"amount": 34823710888228,
"target": {
"tagged_key": {
"key": "a0a04f1f191ea2f16240a995d0c23b7e6ffc81e8dd83cc511f7102bbe7227057",
"view_tag": "ec"
}
}
}
],
"extra": [ 1, 246, 82, 141, 132, 184, 184, 165, 15, 25, 129, 199, 0, 77, 133, 225, 123, 26, 75, 253, 207, 92, 123, 253, 232, 77, 148, 69, 199, 165, 66, 11, 187, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}