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: d8b2c45aeba80c1aebd7639503ec6ba816eeb8566c72e052affed0abb0e71c4b
Tx prefix hash: 3d10cdd9e06753131bc647d02d1dbcf051b70e3b7fa4f2739f2f55765193f410
Tx public key: 0a9ac0f94158f6c3ca8d0ff27c71a4dc907f288647e0f2d831e497481c700ed0
| Timestamp: 1779785456 | Timestamp [UTC]: 2026-05-26 08:50:56 | Age [y:d:h:m:s]: 00:013:16:45:01 |
| Block: 2160 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5726 | RingCT/type: yes/0 |
| Extra: 010a9ac0f94158f6c3ca8d0ff27c71a4dc907f288647e0f2d831e497481c700ed002090000000426697be300 | ||
1 output(s) for total of 35.039781826872 HMNY
| stealth address | amount | amount idx | tag |
| 00: 43e1c85cba6917ce479ddeb29d96df5e49fbff318c4b987c66f739630e4d6a76 | 35.039781826872 | 2494 of 0 | <de> |
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": 2220,
"vin": [ {
"gen": {
"height": 2160
}
}
],
"vout": [ {
"amount": 35039781826872,
"target": {
"tagged_key": {
"key": "43e1c85cba6917ce479ddeb29d96df5e49fbff318c4b987c66f739630e4d6a76",
"view_tag": "de"
}
}
}
],
"extra": [ 1, 10, 154, 192, 249, 65, 88, 246, 195, 202, 141, 15, 242, 124, 113, 164, 220, 144, 127, 40, 134, 71, 224, 242, 216, 49, 228, 151, 72, 28, 112, 14, 208, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}