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: d1d63904884546a081a3b08c9acde86410fa5b3522b276275087668d276cec91
Tx prefix hash: eb1ab8a648e3fbeb4494d662637305a2cd35e2d8a18d9a566e8ae0f737a61d5b
Tx public key: 9edd1b8055d843700c9b1c5e9b0c6c96c92ac49492a337173df77a8d14175804
| Timestamp: 1780055847 | Timestamp [UTC]: 2026-05-29 11:57:27 | Age [y:d:h:m:s]: 00:010:14:52:21 |
| Block: 4452 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3448 | RingCT/type: yes/0 |
| Extra: 019edd1b8055d843700c9b1c5e9b0c6c96c92ac49492a337173df77a8d1417580402090000000326697be300 | ||
1 output(s) for total of 34.886934602015 HMNY
| stealth address | amount | amount idx | tag |
| 00: 811be7ec238b4fa3311036b5407ca46e43d11263ad6b75593f8a4453a27c39ef | 34.886934602015 | 5572 of 0 | <7f> |
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": 4512,
"vin": [ {
"gen": {
"height": 4452
}
}
],
"vout": [ {
"amount": 34886934602015,
"target": {
"tagged_key": {
"key": "811be7ec238b4fa3311036b5407ca46e43d11263ad6b75593f8a4453a27c39ef",
"view_tag": "7f"
}
}
}
],
"extra": [ 1, 158, 221, 27, 128, 85, 216, 67, 112, 12, 155, 28, 94, 155, 12, 108, 150, 201, 42, 196, 148, 146, 163, 55, 23, 61, 247, 122, 141, 20, 23, 88, 4, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}