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: 37df85c08ecf7061e33340a39a4234cfc62ab97bb78a0baff9975ff81c0e1dd4
Tx prefix hash: c6202ae9d3578907c4fe62e8df377073d434dc9acafad82f28e8df400d898a19
Tx public key: dc0e3ba3c42e7dbfa9805831628dd0f12bf33671b62ad89a11000f4911e29706
| Timestamp: 1779721103 | Timestamp [UTC]: 2026-05-25 14:58:23 | Age [y:d:h:m:s]: 00:014:09:48:24 |
| Block: 1757 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6129 | RingCT/type: yes/0 |
| Extra: 01dc0e3ba3c42e7dbfa9805831628dd0f12bf33671b62ad89a11000f4911e29706020900000005ba6d17be00 | ||
1 output(s) for total of 35.066725937917 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9a235798c964748a054e69ebe58cac6c37cf279bf65698bac956d1d29339bcc0 | 35.066725937917 | 1937 of 0 | <62> |
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": 1817,
"vin": [ {
"gen": {
"height": 1757
}
}
],
"vout": [ {
"amount": 35066725937917,
"target": {
"tagged_key": {
"key": "9a235798c964748a054e69ebe58cac6c37cf279bf65698bac956d1d29339bcc0",
"view_tag": "62"
}
}
}
],
"extra": [ 1, 220, 14, 59, 163, 196, 46, 125, 191, 169, 128, 88, 49, 98, 141, 208, 241, 43, 243, 54, 113, 182, 42, 216, 154, 17, 0, 15, 73, 17, 226, 151, 6, 2, 9, 0, 0, 0, 5, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}