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: eb0c3f068303f084388d116e80237d0ae26e51cc2fa013636eb935d37546749a
Tx prefix hash: 6f9dc0a222b7db492286a93df663b0621df14dec95dbb1590ed130e8885ed461
Tx public key: 14c63d11becc6135f15f4288902b134b0ede152aa7acfc856697d797c730456d
| Timestamp: 1780384444 | Timestamp [UTC]: 2026-06-02 07:14:04 | Age [y:d:h:m:s]: 00:006:18:21:53 |
| Block: 5171 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2715 | RingCT/type: yes/0 |
| Extra: 0114c63d11becc6135f15f4288902b134b0ede152aa7acfc856697d797c730456d02090000000126697be300 | ||
1 output(s) for total of 34.839123974964 HMNY
| stealth address | amount | amount idx | tag |
| 00: 987d5072143b64f7a7e8949195861ecc975cfcd12fd5a0c25e3e9e02aae5b0f0 | 34.839123974964 | 6550 of 0 | <18> |
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": 5231,
"vin": [ {
"gen": {
"height": 5171
}
}
],
"vout": [ {
"amount": 34839123974964,
"target": {
"tagged_key": {
"key": "987d5072143b64f7a7e8949195861ecc975cfcd12fd5a0c25e3e9e02aae5b0f0",
"view_tag": "18"
}
}
}
],
"extra": [ 1, 20, 198, 61, 17, 190, 204, 97, 53, 241, 95, 66, 136, 144, 43, 19, 75, 14, 222, 21, 42, 167, 172, 252, 133, 102, 151, 215, 151, 199, 48, 69, 109, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}