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: 438e22444ae742a76717cb4692c63aec9e250ad74c8d1b45f6a6f340cf7a9f33
Tx prefix hash: 132fcb231ab7f0fa94f03aa010b8bcfc416ab1cf83999fbfbaf26426460c841f
Tx public key: dae4fba2dd7954cb5ec4ea668fbdb7d83c09ce2113a32353a026a62386c9877c
| Timestamp: 1780738682 | Timestamp [UTC]: 2026-06-06 09:38:02 | Age [y:d:h:m:s]: 00:002:18:12:56 |
| Block: 6394 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1597 | RingCT/type: yes/0 |
| Extra: 01dae4fba2dd7954cb5ec4ea668fbdb7d83c09ce2113a32353a026a62386c9877c020900000003e49593ff00 | ||
1 output(s) for total of 34.757949826560 HMNY
| stealth address | amount | amount idx | tag |
| 00: b3a9bc34418500220718bf43c4c6ac89e5063d3fece798791c59e7401fc527e7 | 34.757949826560 | 7883 of 0 | <5e> |
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": 6454,
"vin": [ {
"gen": {
"height": 6394
}
}
],
"vout": [ {
"amount": 34757949826560,
"target": {
"tagged_key": {
"key": "b3a9bc34418500220718bf43c4c6ac89e5063d3fece798791c59e7401fc527e7",
"view_tag": "5e"
}
}
}
],
"extra": [ 1, 218, 228, 251, 162, 221, 121, 84, 203, 94, 196, 234, 102, 143, 189, 183, 216, 60, 9, 206, 33, 19, 163, 35, 83, 160, 38, 166, 35, 134, 201, 135, 124, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}