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: 192e98b979f2f80b45ea49fe09fba9a8f1ce7784ee917c88a30a76bd35b4adb6
Tx prefix hash: 8c6317334e054718ba7d166b2db9db2a4241d194252163c82b395f2cd654804c
Tx public key: 38c185e7955a3dc44f5780acf97f8441504682f601b33e9d2d040e624e009a1d
| Timestamp: 1779886218 | Timestamp [UTC]: 2026-05-27 12:50:18 | Age [y:d:h:m:s]: 00:020:19:38:54 |
| Block: 3012 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5733 | RingCT/type: yes/0 |
| Extra: 0138c185e7955a3dc44f5780acf97f8441504682f601b33e9d2d040e624e009a1d02090000000226697be300 | ||
1 output(s) for total of 34.982886230415 HMNY
| stealth address | amount | amount idx | tag |
| 00: 26f15833a3930cd90901f006a3c715c8c7794bf0935791650613e2da5a7dc02e | 34.982886230415 | 3578 of 0 | <f5> |
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": 3072,
"vin": [ {
"gen": {
"height": 3012
}
}
],
"vout": [ {
"amount": 34982886230415,
"target": {
"tagged_key": {
"key": "26f15833a3930cd90901f006a3c715c8c7794bf0935791650613e2da5a7dc02e",
"view_tag": "f5"
}
}
}
],
"extra": [ 1, 56, 193, 133, 231, 149, 90, 61, 196, 79, 87, 128, 172, 249, 127, 132, 65, 80, 70, 130, 246, 1, 179, 62, 157, 45, 4, 14, 98, 78, 0, 154, 29, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}