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: 7de3d42ecff22c0ae72113973307ad175b22c2a0d9cc908464e8a628465db98e
Tx prefix hash: e3430b1989bfb497accc778d2eed257a8e0abe51cdb45157a26601c9bfe7c28b
Tx public key: 26cfa602d22430aa7b459b7557f0fc2ff2d6dc31ce6228c65e5ebeb89f37ae07
| Timestamp: 1780058136 | Timestamp [UTC]: 2026-05-29 12:35:36 | Age [y:d:h:m:s]: 00:014:22:26:40 |
| Block: 4480 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4265 | RingCT/type: yes/0 |
| Extra: 0126cfa602d22430aa7b459b7557f0fc2ff2d6dc31ce6228c65e5ebeb89f37ae0702090000000426697be300 | ||
1 output(s) for total of 34.885071486673 HMNY
| stealth address | amount | amount idx | tag |
| 00: 11a0793600ea108f5654431976aee26b44a5433b01ddf0c22605720f55d70e37 | 34.885071486673 | 5613 of 0 | <e0> |
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": 4540,
"vin": [ {
"gen": {
"height": 4480
}
}
],
"vout": [ {
"amount": 34885071486673,
"target": {
"tagged_key": {
"key": "11a0793600ea108f5654431976aee26b44a5433b01ddf0c22605720f55d70e37",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 38, 207, 166, 2, 210, 36, 48, 170, 123, 69, 155, 117, 87, 240, 252, 47, 242, 214, 220, 49, 206, 98, 40, 198, 94, 94, 190, 184, 159, 55, 174, 7, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}