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: 4fff1707c832f1bdce8eaf040d1924b521f594e65b811b532ab1b6f01d7cc827
Tx prefix hash: 78ffc984a84778bf0a74e9def7c1d3fd2d65a51f736df9e0f4705720fa894ed7
Tx public key: 588aae719bef378b5b6d0e801061c9e44c560c8580c227581f2c69a0b2b7eddd
| Timestamp: 1780694596 | Timestamp [UTC]: 2026-06-05 21:23:16 | Age [y:d:h:m:s]: 00:003:03:23:31 |
| Block: 5947 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1939 | RingCT/type: yes/0 |
| Extra: 01588aae719bef378b5b6d0e801061c9e44c560c8580c227581f2c69a0b2b7eddd020900000001e49593ff00 | ||
1 output(s) for total of 34.787596592281 HMNY
| stealth address | amount | amount idx | tag |
| 00: d0a1fa0317e2a863f119cf475a3a9deb31c19cc1b8343a4b24b3e5fea99c28c7 | 34.787596592281 | 7410 of 0 | <40> |
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": 6007,
"vin": [ {
"gen": {
"height": 5947
}
}
],
"vout": [ {
"amount": 34787596592281,
"target": {
"tagged_key": {
"key": "d0a1fa0317e2a863f119cf475a3a9deb31c19cc1b8343a4b24b3e5fea99c28c7",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 88, 138, 174, 113, 155, 239, 55, 139, 91, 109, 14, 128, 16, 97, 201, 228, 76, 86, 12, 133, 128, 194, 39, 88, 31, 44, 105, 160, 178, 183, 237, 221, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}