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: f6380cd3c1ffdb8deebd32c8fbe64240f94b4e5e9b0c75c29c0d506621a71bb4
Tx prefix hash: 181eaf69b09034e91d6c52b25ba32a2e5cac731c673fb006221804e03c6a1f9b
Tx public key: dd5ca14ea105dd5132589690242bbd4068bfc4e181578f30fbbf80395af142d5
| Timestamp: 1780322829 | Timestamp [UTC]: 2026-06-01 14:07:09 | Age [y:d:h:m:s]: 00:008:03:01:54 |
| Block: 5024 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3710 | RingCT/type: yes/0 |
| Extra: 01dd5ca14ea105dd5132589690242bbd4068bfc4e181578f30fbbf80395af142d502090000001426697be300 | ||
1 output(s) for total of 34.848893556072 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2ecacdd7b7e2714277eaca25333083a0b24384f53a3ff7afd4ecca4142e2abf2 | 34.848893556072 | 6397 of 0 | <aa> |
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": 5084,
"vin": [ {
"gen": {
"height": 5024
}
}
],
"vout": [ {
"amount": 34848893556072,
"target": {
"tagged_key": {
"key": "2ecacdd7b7e2714277eaca25333083a0b24384f53a3ff7afd4ecca4142e2abf2",
"view_tag": "aa"
}
}
}
],
"extra": [ 1, 221, 92, 161, 78, 161, 5, 221, 81, 50, 88, 150, 144, 36, 43, 189, 64, 104, 191, 196, 225, 129, 87, 143, 48, 251, 191, 128, 57, 90, 241, 66, 213, 2, 9, 0, 0, 0, 20, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}