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: 85005eba16d74cb504211ae3f61096403e38d5c787e9b3974f8889c2ef50abca
Tx prefix hash: b28c2980775ec52f918bfe7210c83c211d882e4394bc33064942822c12a42880
Tx public key: a0c76ce3b3937943f6ccffa77dd1caecbde92b71ec088879f0c9d71871fb937d
| Timestamp: 1780032280 | Timestamp [UTC]: 2026-05-29 05:24:40 | Age [y:d:h:m:s]: 00:010:20:11:17 |
| Block: 4211 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3675 | RingCT/type: yes/0 |
| Extra: 01a0c76ce3b3937943f6ccffa77dd1caecbde92b71ec088879f0c9d71871fb937d02090000000626697be300 | ||
1 output(s) for total of 34.902974816471 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5898b39cc61e160c56cc7ae82615c42228a492fa8222d77930313cba341c2fca | 34.902974816471 | 5246 of 0 | <ea> |
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": 4271,
"vin": [ {
"gen": {
"height": 4211
}
}
],
"vout": [ {
"amount": 34902974816471,
"target": {
"tagged_key": {
"key": "5898b39cc61e160c56cc7ae82615c42228a492fa8222d77930313cba341c2fca",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 160, 199, 108, 227, 179, 147, 121, 67, 246, 204, 255, 167, 125, 209, 202, 236, 189, 233, 43, 113, 236, 8, 136, 121, 240, 201, 215, 24, 113, 251, 147, 125, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}