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: 90e866b6aed50586c349e656a4d43c3c417a6bfa6ada0c1fe485f72f15ab4526
Tx prefix hash: f5652c394392c54ef5358131efc0bc94c53c3e4adab8ebda8ef8a0f3d1a0f8c3
Tx public key: 475e86f6c63443d2f5e4c89c6c14a40b5875a3a695f11a7ef71f30b6219d82df
| Timestamp: 1780743909 | Timestamp [UTC]: 2026-06-06 11:05:09 | Age [y:d:h:m:s]: 00:002:14:30:48 |
| Block: 6436 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1450 | RingCT/type: yes/0 |
| Extra: 01475e86f6c63443d2f5e4c89c6c14a40b5875a3a695f11a7ef71f30b6219d82df020900000003e49593ff00 | ||
1 output(s) for total of 34.755165523250 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0dfc6bd585c375c77e0343c4d87f8c243a79268185f0d5f65d1528b64b621a2f | 34.755165523250 | 7929 of 0 | <e0> |
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": 6496,
"vin": [ {
"gen": {
"height": 6436
}
}
],
"vout": [ {
"amount": 34755165523250,
"target": {
"tagged_key": {
"key": "0dfc6bd585c375c77e0343c4d87f8c243a79268185f0d5f65d1528b64b621a2f",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 71, 94, 134, 246, 198, 52, 67, 210, 245, 228, 200, 156, 108, 20, 164, 11, 88, 117, 163, 166, 149, 241, 26, 126, 247, 31, 48, 182, 33, 157, 130, 223, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}