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: 496f318fea4c6cef449ee3b0d086b63fe1a9ee27e2f64e8188f33ae0b147d3ee
Tx prefix hash: f9267d305c6f6e43e0575b83e83798a3c8b380fabaa09648be1e29ce0db0abac
Tx public key: 0588d55e98b1ecd223a2d711dab9455b016b6787edb47b3da2bf9b7ff92e1f4b
| Timestamp: 1779730483 | Timestamp [UTC]: 2026-05-25 17:34:43 | Age [y:d:h:m:s]: 00:022:14:54:29 |
| Block: 1876 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6869 | RingCT/type: yes/0 |
| Extra: 010588d55e98b1ecd223a2d711dab9455b016b6787edb47b3da2bf9b7ff92e1f4b020900000001ba6d17be00 | ||
1 output(s) for total of 35.061377581392 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5062dabf62ac07d445298838f91493047f9efb6e4dae21cc8652eca8cfd31af1 | 35.061377581392 | 2089 of 0 | <b5> |
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": 1936,
"vin": [ {
"gen": {
"height": 1876
}
}
],
"vout": [ {
"amount": 35061377581392,
"target": {
"tagged_key": {
"key": "5062dabf62ac07d445298838f91493047f9efb6e4dae21cc8652eca8cfd31af1",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 5, 136, 213, 94, 152, 177, 236, 210, 35, 162, 215, 17, 218, 185, 69, 91, 1, 107, 103, 135, 237, 180, 123, 61, 162, 191, 155, 127, 249, 46, 31, 75, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}