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: ac83975a8e6540a06acdfeb5b9b3a7ca296fa1f484119ed95a6273ad37830c29
Tx prefix hash: 9d2c39f7d14ae639f43ea6750d36277998d901bf7d4c33bcdab81f6cfcf9307b
Tx public key: e08cd96bcba563c8a6c9b04f282f9d9dc99c1578d9fe09d12db9bdf5bfa2ba45
| Timestamp: 1779910850 | Timestamp [UTC]: 2026-05-27 19:40:50 | Age [y:d:h:m:s]: 00:012:03:38:03 |
| Block: 3243 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4643 | RingCT/type: yes/0 |
| Extra: 01e08cd96bcba563c8a6c9b04f282f9d9dc99c1578d9fe09d12db9bdf5bfa2ba4502090000000226697be300 | ||
1 output(s) for total of 34.978089037359 HMNY
| stealth address | amount | amount idx | tag |
| 00: f1469873b354cafbf67b4f3be373ead19ea0fe783e61a630f5b2719533a1ce80 | 34.978089037359 | 3889 of 0 | <50> |
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": 3303,
"vin": [ {
"gen": {
"height": 3243
}
}
],
"vout": [ {
"amount": 34978089037359,
"target": {
"tagged_key": {
"key": "f1469873b354cafbf67b4f3be373ead19ea0fe783e61a630f5b2719533a1ce80",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 224, 140, 217, 107, 203, 165, 99, 200, 166, 201, 176, 79, 40, 47, 157, 157, 201, 156, 21, 120, 217, 254, 9, 209, 45, 185, 189, 245, 191, 162, 186, 69, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}