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: fd11d84132a3a200714929c0b1fcd6673ba436e5d042784a284aeb799585e356
Tx prefix hash: ef85e9677b20dd0eaccf459ff116dbcf7caa9114360266b0acf8212a59f3d652
Tx public key: b8468ea628fa1db03b9b2805867667dc6c86e6a6a779998aa596d80ccd311208
| Timestamp: 1780693413 | Timestamp [UTC]: 2026-06-05 21:03:33 | Age [y:d:h:m:s]: 00:003:04:32:24 |
| Block: 5869 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2017 | RingCT/type: yes/0 |
| Extra: 01b8468ea628fa1db03b9b2805867667dc6c86e6a6a779998aa596d80ccd311208020900000001e49593ff00 | ||
1 output(s) for total of 34.792772444056 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3c0eb4aa4c8c9e225371098b4ebf46b97782bc43125ba0aac4501e0b7655586b | 34.792772444056 | 7328 of 0 | <c7> |
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": 5929,
"vin": [ {
"gen": {
"height": 5869
}
}
],
"vout": [ {
"amount": 34792772444056,
"target": {
"tagged_key": {
"key": "3c0eb4aa4c8c9e225371098b4ebf46b97782bc43125ba0aac4501e0b7655586b",
"view_tag": "c7"
}
}
}
],
"extra": [ 1, 184, 70, 142, 166, 40, 250, 29, 176, 59, 155, 40, 5, 134, 118, 103, 220, 108, 134, 230, 166, 167, 121, 153, 138, 165, 150, 216, 12, 205, 49, 18, 8, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}