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: 51f44abe8391e7a4c54b4bf74bcbb81b9a3935cd5ca8b62f3b5fe3fbfff06911
Tx prefix hash: 3d695ddf2847422a237cd08b53c4263f0310733093cafed00a990601b16d82c2
Tx public key: e8e01007a3d7217bd23bfa595da5213bcc0c5a4e7aea5205ba8300e90fb27ef5
| Timestamp: 1780052753 | Timestamp [UTC]: 2026-05-29 11:05:53 | Age [y:d:h:m:s]: 00:010:12:13:00 |
| Block: 4416 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3470 | RingCT/type: yes/0 |
| Extra: 01e8e01007a3d7217bd23bfa595da5213bcc0c5a4e7aea5205ba8300e90fb27ef502090000000626697be300 | ||
1 output(s) for total of 34.889330182237 HMNY
| stealth address | amount | amount idx | tag |
| 00: 55311e4c1928dcbe989f9204a74f68c1f0137ab020f0e554815402896afb03bf | 34.889330182237 | 5526 of 0 | <20> |
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": 4476,
"vin": [ {
"gen": {
"height": 4416
}
}
],
"vout": [ {
"amount": 34889330182237,
"target": {
"tagged_key": {
"key": "55311e4c1928dcbe989f9204a74f68c1f0137ab020f0e554815402896afb03bf",
"view_tag": "20"
}
}
}
],
"extra": [ 1, 232, 224, 16, 7, 163, 215, 33, 123, 210, 59, 250, 89, 93, 165, 33, 59, 204, 12, 90, 78, 122, 234, 82, 5, 186, 131, 0, 233, 15, 178, 126, 245, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}