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: e008acccce509016373cf56d24bde6182ee967960bcf9d65fd1b7b6c5a5484e1
Tx prefix hash: 7894fc1a29d649954a3a3d00f6a55a611ed3f79f273098bf5307b1ef830d492b
Tx public key: dc84cb117ac3fcd9a45e026d9d1c729fd66a38af1c24a9819c928baf5e5d22da
| Timestamp: 1780999253 | Timestamp [UTC]: 2026-06-09 10:00:53 | Age [y:d:h:m:s]: 00:000:06:51:03 |
| Block: 8409 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 314 | RingCT/type: yes/0 |
| Extra: 01dc84cb117ac3fcd9a45e026d9d1c729fd66a38af1c24a9819c928baf5e5d22da020900000002e49593ff00 | ||
1 output(s) for total of 34.624620587074 HMNY
| stealth address | amount | amount idx | tag |
| 00: c72bba0cbe89f52fd102533daae1ef70f5e55277a9e26079259ad7a5783526dd | 34.624620587074 | 10395 of 0 | <0a> |
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": 8469,
"vin": [ {
"gen": {
"height": 8409
}
}
],
"vout": [ {
"amount": 34624620587074,
"target": {
"tagged_key": {
"key": "c72bba0cbe89f52fd102533daae1ef70f5e55277a9e26079259ad7a5783526dd",
"view_tag": "0a"
}
}
}
],
"extra": [ 1, 220, 132, 203, 17, 122, 195, 252, 217, 164, 94, 2, 109, 157, 28, 114, 159, 214, 106, 56, 175, 28, 36, 169, 129, 156, 146, 139, 175, 94, 93, 34, 218, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}