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: d6daae713aeb14da648dd37af03c88631f74b383abf1f19a40cb8f9e3c33b0ee
Tx prefix hash: 56da9887d2008086b3759012700c14b09f9dac0656dbc03d36508abb9b1f5749
Tx public key: 1082be1ae05ed4e83a4adbb4ed34b3175afd6d98c06ffb370b833f7d4e2b83d8
| Timestamp: 1781025120 | Timestamp [UTC]: 2026-06-09 17:12:00 | Age [y:d:h:m:s]: 00:006:00:04:25 |
| Block: 8733 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 12 | RingCT/type: yes/0 |
| Extra: 011082be1ae05ed4e83a4adbb4ed34b3175afd6d98c06ffb370b833f7d4e2b83d8020900000003e49593ff00 | ||
1 output(s) for total of 34.603229820731 HMNY
| stealth address | amount | amount idx | tag |
| 00: 40cbba5813b715e3b947c81c5a13fb8dfb3fcb2000384f602b1facc5d68931c3 | 34.603229820731 | 10803 of 0 | <fd> |
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": 8793,
"vin": [ {
"gen": {
"height": 8733
}
}
],
"vout": [ {
"amount": 34603229820731,
"target": {
"tagged_key": {
"key": "40cbba5813b715e3b947c81c5a13fb8dfb3fcb2000384f602b1facc5d68931c3",
"view_tag": "fd"
}
}
}
],
"extra": [ 1, 16, 130, 190, 26, 224, 94, 212, 232, 58, 74, 219, 180, 237, 52, 179, 23, 90, 253, 109, 152, 192, 111, 251, 55, 11, 131, 63, 125, 78, 43, 131, 216, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}