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: ec7892a30fe4a472f40dfc981ec0929b30d26f6e368e0af4869791b9aa80160d
Tx prefix hash: 1610da15259f2d2020d9d50f799711ea75b009e4d0ee3fcda76f02d9b84f4cbc
Tx public key: 74f47d4c86957ac4d9290c8fdcf8c34af16ef30262390618a3e19630eff85dde
| Timestamp: 1780756020 | Timestamp [UTC]: 2026-06-06 14:27:00 | Age [y:d:h:m:s]: 00:002:11:08:57 |
| Block: 6533 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1353 | RingCT/type: yes/0 |
| Extra: 0174f47d4c86957ac4d9290c8fdcf8c34af16ef30262390618a3e19630eff85dde020900000004e49593ff00 | ||
1 output(s) for total of 34.748735960821 HMNY
| stealth address | amount | amount idx | tag |
| 00: 59e5a0a1ce524d258461fc56af2c1680c3b665fb66bbbeeb910a20eec07b7bdf | 34.748735960821 | 8037 of 0 | <5f> |
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": 6593,
"vin": [ {
"gen": {
"height": 6533
}
}
],
"vout": [ {
"amount": 34748735960821,
"target": {
"tagged_key": {
"key": "59e5a0a1ce524d258461fc56af2c1680c3b665fb66bbbeeb910a20eec07b7bdf",
"view_tag": "5f"
}
}
}
],
"extra": [ 1, 116, 244, 125, 76, 134, 149, 122, 196, 217, 41, 12, 143, 220, 248, 195, 74, 241, 110, 243, 2, 98, 57, 6, 24, 163, 225, 150, 48, 239, 248, 93, 222, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}