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: 9702843355a65e05804426ea1814d7ef555ea21d885f6793978a990b90abb1e9
Tx prefix hash: e67b58d7a8deb0a363ad84d50da9f67d1ae8a8a97177f690c914df37fb165a85
Tx public key: d0f9c00c178edb3aa603501db0637c80ce543c1f3d567c37c54d0d076f7a1a64
| Timestamp: 1779770961 | Timestamp [UTC]: 2026-05-26 04:49:21 | Age [y:d:h:m:s]: 00:013:22:00:27 |
| Block: 2011 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5888 | RingCT/type: yes/0 |
| Extra: 01d0f9c00c178edb3aa603501db0637c80ce543c1f3d567c37c54d0d076f7a1a6402090000000326697be300 | ||
1 output(s) for total of 35.049741380445 HMNY
| stealth address | amount | amount idx | tag |
| 00: b2278cdb7028d8b28710efa6bba8e4fdee369a642123e7b55a6595a4f97593cc | 35.049741380445 | 2297 of 0 | <2f> |
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": 2071,
"vin": [ {
"gen": {
"height": 2011
}
}
],
"vout": [ {
"amount": 35049741380445,
"target": {
"tagged_key": {
"key": "b2278cdb7028d8b28710efa6bba8e4fdee369a642123e7b55a6595a4f97593cc",
"view_tag": "2f"
}
}
}
],
"extra": [ 1, 208, 249, 192, 12, 23, 142, 219, 58, 166, 3, 80, 29, 176, 99, 124, 128, 206, 84, 60, 31, 61, 86, 124, 55, 197, 77, 13, 7, 111, 122, 26, 100, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}