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: ad7ac87ed8f763332ab7aa02f46c169e95f20565758f47e716018043a82b9ade
Tx prefix hash: bc8157246d10f8875f6ebe4f621231f5b89f082e0048f5a17c4e1229028a8c74
Tx public key: dde86dc9970d0ed1b30d252c28a1aebc3d41579b3889fbf3ea981a50213f3f58
| Timestamp: 1780389070 | Timestamp [UTC]: 2026-06-02 08:31:10 | Age [y:d:h:m:s]: 00:006:18:18:38 |
| Block: 5194 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2726 | RingCT/type: yes/0 |
| Extra: 01dde86dc9970d0ed1b30d252c28a1aebc3d41579b3889fbf3ea981a50213f3f5802090000000126697be300 | ||
1 output(s) for total of 34.837595648854 HMNY
| stealth address | amount | amount idx | tag |
| 00: 11fc849beaaacfafed9bfa0626a9cfc4458c08d56876028c9e5f8eb6450857e7 | 34.837595648854 | 6575 of 0 | <3f> |
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": 5254,
"vin": [ {
"gen": {
"height": 5194
}
}
],
"vout": [ {
"amount": 34837595648854,
"target": {
"tagged_key": {
"key": "11fc849beaaacfafed9bfa0626a9cfc4458c08d56876028c9e5f8eb6450857e7",
"view_tag": "3f"
}
}
}
],
"extra": [ 1, 221, 232, 109, 201, 151, 13, 14, 209, 179, 13, 37, 44, 40, 161, 174, 188, 61, 65, 87, 155, 56, 137, 251, 243, 234, 152, 26, 80, 33, 63, 63, 88, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}