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: cdb717c5e25c857ef7e78757d3747519ff1861f139c841caf846900808009dcd
Tx prefix hash: 33dbb649a1bca7f8b40e73c04b30b3d64c0813239aee062a1e713113e3363ed1
Tx public key: d6a04b01da4a2f72adc7f0fcbdb6bd77f35109a0485d036bbaaa2b3673a78d00
| Timestamp: 1779451334 | Timestamp [UTC]: 2026-05-22 12:02:14 | Age [y:d:h:m:s]: 00:017:14:47:34 |
| Block: 327 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7593 | RingCT/type: yes/0 |
| Extra: 01d6a04b01da4a2f72adc7f0fcbdb6bd77f35109a0485d036bbaaa2b3673a78d000209000000044438f87f00 | ||
1 output(s) for total of 35.162501378685 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5a65e045d8294be690b106cc8c9da63c282b72b28f92d4b49d1c6b635d4798bc | 35.162501378685 | 323 of 0 | <91> |
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": 387,
"vin": [ {
"gen": {
"height": 327
}
}
],
"vout": [ {
"amount": 35162501378685,
"target": {
"tagged_key": {
"key": "5a65e045d8294be690b106cc8c9da63c282b72b28f92d4b49d1c6b635d4798bc",
"view_tag": "91"
}
}
}
],
"extra": [ 1, 214, 160, 75, 1, 218, 74, 47, 114, 173, 199, 240, 252, 189, 182, 189, 119, 243, 81, 9, 160, 72, 93, 3, 107, 186, 170, 43, 54, 115, 167, 141, 0, 2, 9, 0, 0, 0, 4, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}