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: 88359868816825df1b7d9371c08d99af704d6379eb5850b6d503a5ca16cd9221
Tx prefix hash: 0a8677206c88f1474e79bf3cbe69fdd177bc0a1d470f14820b53cbf1b3405845
Tx public key: a56720cfb1f43dba270d4bf20b34c15f094b392f8cfccc276d00a454584f4f5f
| Timestamp: 1780734526 | Timestamp [UTC]: 2026-06-06 08:28:46 | Age [y:d:h:m:s]: 00:002:19:22:12 |
| Block: 6351 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1601 | RingCT/type: yes/0 |
| Extra: 01a56720cfb1f43dba270d4bf20b34c15f094b392f8cfccc276d00a454584f4f5f020900000001e49593ff00 | ||
1 output(s) for total of 34.760800653892 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6d0d48fd261085646e01fd348f3e1229743303dcddaf0c0ee4130a9cf0ee3d70 | 34.760800653892 | 7838 of 0 | <66> |
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": 6411,
"vin": [ {
"gen": {
"height": 6351
}
}
],
"vout": [ {
"amount": 34760800653892,
"target": {
"tagged_key": {
"key": "6d0d48fd261085646e01fd348f3e1229743303dcddaf0c0ee4130a9cf0ee3d70",
"view_tag": "66"
}
}
}
],
"extra": [ 1, 165, 103, 32, 207, 177, 244, 61, 186, 39, 13, 75, 242, 11, 52, 193, 95, 9, 75, 57, 47, 140, 252, 204, 39, 109, 0, 164, 84, 88, 79, 79, 95, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}