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: b5e658c955dcc8bc13c0d69d350655ad17e1104a85d4ef6ac0889fb51b14c83a
Tx prefix hash: b24e72a4fdaee2f593c670fa07a66587fb76871bcb6c80ba3106990fb6362687
Tx public key: d363b64470044df4eba4378798ad688aaa7cf7ceb62a16df8b81fae89590ba0a
| Timestamp: 1780997880 | Timestamp [UTC]: 2026-06-09 09:38:00 | Age [y:d:h:m:s]: 00:000:06:21:44 |
| Block: 8387 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 304 | RingCT/type: yes/0 |
| Extra: 01d363b64470044df4eba4378798ad688aaa7cf7ceb62a16df8b81fae89590ba0a020900000005e49593ff00 | ||
1 output(s) for total of 34.626073525844 HMNY
| stealth address | amount | amount idx | tag |
| 00: d3c8f8a789d4e123aed1a77ac76062abf6eac99214b4ecd38789cd74d4e196bf | 34.626073525844 | 10367 of 0 | <a2> |
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": 8447,
"vin": [ {
"gen": {
"height": 8387
}
}
],
"vout": [ {
"amount": 34626073525844,
"target": {
"tagged_key": {
"key": "d3c8f8a789d4e123aed1a77ac76062abf6eac99214b4ecd38789cd74d4e196bf",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 211, 99, 182, 68, 112, 4, 77, 244, 235, 164, 55, 135, 152, 173, 104, 138, 170, 124, 247, 206, 182, 42, 22, 223, 139, 129, 250, 232, 149, 144, 186, 10, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}