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: 38bbe604599cb008b5e3c8bb9fc22e786288e55a8fdf69dc532ee9b19b6bfdd1
Tx prefix hash: 66a865b5a404ad3da1c4cc3d7224dcac48aa1f5d8adf772fa338910670d008ca
Tx public key: 8dde5458f39d8f9ab21dbc8f54aafea243237c949b5ee26660e117d419d44c14
| Timestamp: 1780063443 | Timestamp [UTC]: 2026-05-29 14:04:03 | Age [y:d:h:m:s]: 00:011:03:05:00 |
| Block: 4553 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4181 | RingCT/type: yes/0 |
| Extra: 018dde5458f39d8f9ab21dbc8f54aafea243237c949b5ee26660e117d419d44c1402090000000b26697be300 | ||
1 output(s) for total of 34.880214546661 HMNY
| stealth address | amount | amount idx | tag |
| 00: 667cd0fa5a071861d813d4e33300eaccef359775acbc3d6868d0968f8ca65adf | 34.880214546661 | 5714 of 0 | <a3> |
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": 4613,
"vin": [ {
"gen": {
"height": 4553
}
}
],
"vout": [ {
"amount": 34880214546661,
"target": {
"tagged_key": {
"key": "667cd0fa5a071861d813d4e33300eaccef359775acbc3d6868d0968f8ca65adf",
"view_tag": "a3"
}
}
}
],
"extra": [ 1, 141, 222, 84, 88, 243, 157, 143, 154, 178, 29, 188, 143, 84, 170, 254, 162, 67, 35, 124, 148, 155, 94, 226, 102, 96, 225, 23, 212, 25, 212, 76, 20, 2, 9, 0, 0, 0, 11, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}