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: bce03538985cd7fcc24115f37fc082cac9da9087c67dd87e29843c32b9b29e4e
Tx prefix hash: 11da4a98cf99d30a50a31494c1b33b4e1a07ec93220b11a3cd3a77848d83b41b
Tx public key: c2d353309249ab9b1325b1d716b3a803e73694c610c512f84d14c0038277e219
| Timestamp: 1780807739 | Timestamp [UTC]: 2026-06-07 04:48:59 | Age [y:d:h:m:s]: 00:002:12:20:04 |
| Block: 6971 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1764 | RingCT/type: yes/0 |
| Extra: 01c2d353309249ab9b1325b1d716b3a803e73694c610c512f84d14c0038277e219020900000001e49593ff00 | ||
1 output(s) for total of 34.719718311914 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1e12c36fa09e2095f2d7a0c9e7d9f1b51f6e499abc5183e29b9fcfba4bd31662 | 34.719718311914 | 8597 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": 7031,
"vin": [ {
"gen": {
"height": 6971
}
}
],
"vout": [ {
"amount": 34719718311914,
"target": {
"tagged_key": {
"key": "1e12c36fa09e2095f2d7a0c9e7d9f1b51f6e499abc5183e29b9fcfba4bd31662",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 194, 211, 83, 48, 146, 73, 171, 155, 19, 37, 177, 215, 22, 179, 168, 3, 231, 54, 148, 198, 16, 197, 18, 248, 77, 20, 192, 3, 130, 119, 226, 25, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}