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: 0b5952dca0cc31a06f2543ce8111441aac64779f57ca5082cf6ed45b8f794e77
Tx prefix hash: d35cf6a31839eb6d2a6d32c47565b9db5f95f69db72512d767cb038d89207947
Tx public key: 9d4136781ec51b460c8824f826399df4d22a1fdcaa1d39e269410e7c933c89c9
| Timestamp: 1780053944 | Timestamp [UTC]: 2026-05-29 11:25:44 | Age [y:d:h:m:s]: 00:010:13:21:03 |
| Block: 4424 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3462 | RingCT/type: yes/0 |
| Extra: 019d4136781ec51b460c8824f826399df4d22a1fdcaa1d39e269410e7c933c89c902090000000526697be300 | ||
1 output(s) for total of 34.888797816861 HMNY
| stealth address | amount | amount idx | tag |
| 00: aede6990fe12e81ec528d29a72ccf0bb8937a8888b7ced8a2558012363e091cf | 34.888797816861 | 5538 of 0 | <73> |
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": 4484,
"vin": [ {
"gen": {
"height": 4424
}
}
],
"vout": [ {
"amount": 34888797816861,
"target": {
"tagged_key": {
"key": "aede6990fe12e81ec528d29a72ccf0bb8937a8888b7ced8a2558012363e091cf",
"view_tag": "73"
}
}
}
],
"extra": [ 1, 157, 65, 54, 120, 30, 197, 27, 70, 12, 136, 36, 248, 38, 57, 157, 244, 210, 42, 31, 220, 170, 29, 57, 226, 105, 65, 14, 124, 147, 60, 137, 201, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}