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: 66b1df2249b4e4d118c1cdc12261113fc141445fe8036030cda8935381be6828
Tx prefix hash: 0f29e0c87c52f8cae66466e87ea0a3e962e9e2e937f51fcd15066517f7f57e3b
Tx public key: 1e8a6ac752695a0b9f84ad6708b013950bd472614a64ed61229c287b68f24a66
| Timestamp: 1780687217 | Timestamp [UTC]: 2026-06-05 19:20:17 | Age [y:d:h:m:s]: 00:003:03:58:36 |
| Block: 5469 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2417 | RingCT/type: yes/0 |
| Extra: 011e8a6ac752695a0b9f84ad6708b013950bd472614a64ed61229c287b68f24a66020900000001e49593ff00 | ||
1 output(s) for total of 34.819327376777 HMNY
| stealth address | amount | amount idx | tag |
| 00: 773bd45ee178af2b7cb1ea332b7a5d20fb7c58a1e9648d0c040c2337131bfa4b | 34.819327376777 | 6908 of 0 | <f8> |
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": 5529,
"vin": [ {
"gen": {
"height": 5469
}
}
],
"vout": [ {
"amount": 34819327376777,
"target": {
"tagged_key": {
"key": "773bd45ee178af2b7cb1ea332b7a5d20fb7c58a1e9648d0c040c2337131bfa4b",
"view_tag": "f8"
}
}
}
],
"extra": [ 1, 30, 138, 106, 199, 82, 105, 90, 11, 159, 132, 173, 103, 8, 176, 19, 149, 11, 212, 114, 97, 74, 100, 237, 97, 34, 156, 40, 123, 104, 242, 74, 102, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}