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: 0c02360ad9ab47abc7943170685b8764c11ee4b70c16e55d04365a29be8d7425
Tx prefix hash: daae5daeb0f334fbe5a5edb324363abe421f3c66fcefcb8f5fca25d581cf4253
Tx public key: 6bdf5622b1a4c391d1fcc90578cc72d8d8c62b4a9e1bbe7a7ded01ad0b5f9489
| Timestamp: 1779444258 | Timestamp [UTC]: 2026-05-22 10:04:18 | Age [y:d:h:m:s]: 00:017:16:45:30 |
| Block: 250 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7650 | RingCT/type: yes/0 |
| Extra: 016bdf5622b1a4c391d1fcc90578cc72d8d8c62b4a9e1bbe7a7ded01ad0b5f94890209000000014438f87f00 | ||
1 output(s) for total of 35.167665933317 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7117b1557a41a19910785041047777fa33b3b02c00ec951455a4f3557ea4edb6 | 35.167665933317 | 246 of 0 | <d3> |
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": 310,
"vin": [ {
"gen": {
"height": 250
}
}
],
"vout": [ {
"amount": 35167665933317,
"target": {
"tagged_key": {
"key": "7117b1557a41a19910785041047777fa33b3b02c00ec951455a4f3557ea4edb6",
"view_tag": "d3"
}
}
}
],
"extra": [ 1, 107, 223, 86, 34, 177, 164, 195, 145, 209, 252, 201, 5, 120, 204, 114, 216, 216, 198, 43, 74, 158, 27, 190, 122, 125, 237, 1, 173, 11, 95, 148, 137, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}