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: b771b24d2853eaf077edcdc61d20a55b4aca3e6e990600b4bd249f6156f81476
Tx prefix hash: d1e03fbcceab5d80bb355f7bc741bd8b0b8e0a7ed998ad2fef1a51e2e3e14199
Tx public key: 9081b3722848fbbb74e5cb70ff2b60f884c073232fef114ad39dd58aff9bc3dd
| Timestamp: 1780117272 | Timestamp [UTC]: 2026-05-30 05:01:12 | Age [y:d:h:m:s]: 00:009:21:39:24 |
| Block: 4880 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3017 | RingCT/type: yes/0 |
| Extra: 019081b3722848fbbb74e5cb70ff2b60f884c073232fef114ad39dd58aff9bc3dd02090000000926697be300 | ||
1 output(s) for total of 34.861082414258 HMNY
| stealth address | amount | amount idx | tag |
| 00: ad0f29f6b0a72ae09820427eacae03de63c7faeb2ef3c15846384f88626d4b68 | 34.861082414258 | 6172 of 0 | <e7> |
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": 4940,
"vin": [ {
"gen": {
"height": 4880
}
}
],
"vout": [ {
"amount": 34861082414258,
"target": {
"tagged_key": {
"key": "ad0f29f6b0a72ae09820427eacae03de63c7faeb2ef3c15846384f88626d4b68",
"view_tag": "e7"
}
}
}
],
"extra": [ 1, 144, 129, 179, 114, 40, 72, 251, 187, 116, 229, 203, 112, 255, 43, 96, 248, 132, 192, 115, 35, 47, 239, 17, 74, 211, 157, 213, 138, 255, 155, 195, 221, 2, 9, 0, 0, 0, 9, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}