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: 882fac5cefc13050633d3cf658f5a6cedc9b474291ed2df9784f95c4b26bb138
Tx prefix hash: 5805d84e8a180bf73b93a40896f932357b0a31528d3d25d744b601102ab8e1ed
Tx public key: a01ba74bbbc391340e4f578059af9cee03ee8689d0a80dae6a79a922c3e3e3fe
| Timestamp: 1779643547 | Timestamp [UTC]: 2026-05-24 17:25:47 | Age [y:d:h:m:s]: 00:015:09:14:49 |
| Block: 1415 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6481 | RingCT/type: yes/0 |
| Extra: 01a01ba74bbbc391340e4f578059af9cee03ee8689d0a80dae6a79a922c3e3e3fe020900000001ba6d17be00 | ||
1 output(s) for total of 35.089607911381 HMNY
| stealth address | amount | amount idx | tag |
| 00: 18d98e88354d731a7fd64f7b8327567c8b9d86fb176953aed3ef8e3e84a19f30 | 35.089607911381 | 1567 of 0 | <f6> |
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": 1475,
"vin": [ {
"gen": {
"height": 1415
}
}
],
"vout": [ {
"amount": 35089607911381,
"target": {
"tagged_key": {
"key": "18d98e88354d731a7fd64f7b8327567c8b9d86fb176953aed3ef8e3e84a19f30",
"view_tag": "f6"
}
}
}
],
"extra": [ 1, 160, 27, 167, 75, 187, 195, 145, 52, 14, 79, 87, 128, 89, 175, 156, 238, 3, 238, 134, 137, 208, 168, 13, 174, 106, 121, 169, 34, 195, 227, 227, 254, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}