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: fc6f01150c2ec15b5939251fa29e9afb8ee2ba0c5499291fd4f193d961436c17
Tx prefix hash: c492d14e917dc0fea6a137dbf44e6f4f22bef13e8e7de96527226fe5a3a3b253
Tx public key: 364781d6cd3bedbdaeba34d1a5caa11d6a04027d21571589c1d68c7a7ee6e543
| Timestamp: 1779939670 | Timestamp [UTC]: 2026-05-28 03:41:10 | Age [y:d:h:m:s]: 00:011:21:54:47 |
| Block: 3474 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4412 | RingCT/type: yes/0 |
| Extra: 01364781d6cd3bedbdaeba34d1a5caa11d6a04027d21571589c1d68c7a7ee6e54302090000000226697be300 | ||
1 output(s) for total of 34.952073032419 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0c4a5e2ca5eb9503f4a0600afda4dc785cbb3b83658526a75ac58ee1872179d5 | 34.952073032419 | 4193 of 0 | <ab> |
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": 3534,
"vin": [ {
"gen": {
"height": 3474
}
}
],
"vout": [ {
"amount": 34952073032419,
"target": {
"tagged_key": {
"key": "0c4a5e2ca5eb9503f4a0600afda4dc785cbb3b83658526a75ac58ee1872179d5",
"view_tag": "ab"
}
}
}
],
"extra": [ 1, 54, 71, 129, 214, 205, 59, 237, 189, 174, 186, 52, 209, 165, 202, 161, 29, 106, 4, 2, 125, 33, 87, 21, 137, 193, 214, 140, 122, 126, 230, 229, 67, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}