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: a7f5e01c232648d52c82c921d4bc38f429cc33e74cbfec4672b735fac820116b
Tx prefix hash: c2ed2628ec7112cc595e34a1a7844d53c4f716f0c8aba6558ad368e892f51ebf
Tx public key: 08c2133678ceb7224fa540e09a8a3328265e5f92b1a87a7429ee9601cb3d220e
| Timestamp: 1780061121 | Timestamp [UTC]: 2026-05-29 13:25:21 | Age [y:d:h:m:s]: 00:010:09:53:32 |
| Block: 4524 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3362 | RingCT/type: yes/0 |
| Extra: 0108c2133678ceb7224fa540e09a8a3328265e5f92b1a87a7429ee9601cb3d220e02090000000126697be300 | ||
1 output(s) for total of 34.882143935018 HMNY
| stealth address | amount | amount idx | tag |
| 00: cbcbf60a4a88b94c9f3800991a9ccd16e7989a7dabaf1a2cc33f4c6997520b7e | 34.882143935018 | 5672 of 0 | <90> |
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": 4584,
"vin": [ {
"gen": {
"height": 4524
}
}
],
"vout": [ {
"amount": 34882143935018,
"target": {
"tagged_key": {
"key": "cbcbf60a4a88b94c9f3800991a9ccd16e7989a7dabaf1a2cc33f4c6997520b7e",
"view_tag": "90"
}
}
}
],
"extra": [ 1, 8, 194, 19, 54, 120, 206, 183, 34, 79, 165, 64, 224, 154, 138, 51, 40, 38, 94, 95, 146, 177, 168, 122, 116, 41, 238, 150, 1, 203, 61, 34, 14, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}