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: ac2e37d94f73e5d79a888e2169c4f0b2e00192469652f2a0b38ef0d9c1052064
Tx prefix hash: d902cd9134f7f6b5c88c1979a6dd24941918fe3eddaa081d62ac6b2d76215ca8
Tx public key: a3a1879550e8205e2d550a6208590fe5f32925caf29b275cb8cb4f8d7aa3dd8f
| Timestamp: 1780052131 | Timestamp [UTC]: 2026-05-29 10:55:31 | Age [y:d:h:m:s]: 00:010:15:45:05 |
| Block: 4410 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3487 | RingCT/type: yes/0 |
| Extra: 01a3a1879550e8205e2d550a6208590fe5f32925caf29b275cb8cb4f8d7aa3dd8f02090000000426697be300 | ||
1 output(s) for total of 34.889729461600 HMNY
| stealth address | amount | amount idx | tag |
| 00: 15363223af2ef88079b1fc415360a84ec12b1f736a8fb76a989c37f818232424 | 34.889729461600 | 5518 of 0 | <d4> |
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": 4470,
"vin": [ {
"gen": {
"height": 4410
}
}
],
"vout": [ {
"amount": 34889729461600,
"target": {
"tagged_key": {
"key": "15363223af2ef88079b1fc415360a84ec12b1f736a8fb76a989c37f818232424",
"view_tag": "d4"
}
}
}
],
"extra": [ 1, 163, 161, 135, 149, 80, 232, 32, 94, 45, 85, 10, 98, 8, 89, 15, 229, 243, 41, 37, 202, 242, 155, 39, 92, 184, 203, 79, 141, 122, 163, 221, 143, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}