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: dbb3e06525e0489af928efcdbcc57f25e0c3102d4693d01347054ef641136cf5
Tx prefix hash: 557aeb4d4f89822c4a464dc71f22107017f4fd519fa19c5e4d5693b5200689e7
Tx public key: d89d3cd4f89329b850edb3a67cb2704b9da5aeb4c737e1515d7c8aaf01cb47c8
| Timestamp: 1779844316 | Timestamp [UTC]: 2026-05-27 01:11:56 | Age [y:d:h:m:s]: 00:013:00:24:01 |
| Block: 2432 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5454 | RingCT/type: yes/0 |
| Extra: 01d89d3cd4f89329b850edb3a67cb2704b9da5aeb4c737e1515d7c8aaf01cb47c802090000000226697be300 | ||
1 output(s) for total of 35.021607926498 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5a1d559e52475e2c2aa9804dd1d5fe52ce314d61617dbaf580b78caa2043c8b0 | 35.021607926498 | 2858 of 0 | <15> |
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": 2492,
"vin": [ {
"gen": {
"height": 2432
}
}
],
"vout": [ {
"amount": 35021607926498,
"target": {
"tagged_key": {
"key": "5a1d559e52475e2c2aa9804dd1d5fe52ce314d61617dbaf580b78caa2043c8b0",
"view_tag": "15"
}
}
}
],
"extra": [ 1, 216, 157, 60, 212, 248, 147, 41, 184, 80, 237, 179, 166, 124, 178, 112, 75, 157, 165, 174, 180, 199, 55, 225, 81, 93, 124, 138, 175, 1, 203, 71, 200, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}