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: b0c9674cd31af8a2cb5b81bad0db4c1da16c75539c1f35b28e3c409f04802fcb
Tx prefix hash: 8c6c46207384643917ad317c0d2952a8a6195ca28187e76a5553d11c286d92cb
Tx public key: 2b0e053605f9106ad2d77240cb6a34a633aecf8d3bd878c95fe1d713d4e00537
| Timestamp: 1781014493 | Timestamp [UTC]: 2026-06-09 14:14:53 | Age [y:d:h:m:s]: 00:006:01:23:58 |
| Block: 8620 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 125 | RingCT/type: yes/0 |
| Extra: 012b0e053605f9106ad2d77240cb6a34a633aecf8d3bd878c95fe1d713d4e00537020900000001e49593ff00 | ||
1 output(s) for total of 34.610688679430 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6cf2a0f25361d3992972eafc7c6d14f7de48703ac46e6641eeeae200a4fe0123 | 34.610688679430 | 10654 of 0 | <9b> |
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": 8680,
"vin": [ {
"gen": {
"height": 8620
}
}
],
"vout": [ {
"amount": 34610688679430,
"target": {
"tagged_key": {
"key": "6cf2a0f25361d3992972eafc7c6d14f7de48703ac46e6641eeeae200a4fe0123",
"view_tag": "9b"
}
}
}
],
"extra": [ 1, 43, 14, 5, 54, 5, 249, 16, 106, 210, 215, 114, 64, 203, 106, 52, 166, 51, 174, 207, 141, 59, 216, 120, 201, 95, 225, 215, 19, 212, 224, 5, 55, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}