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: 33b3d1a4308f20497e4f486889046ee9396636f2daa716ebdd18a506e2e8d011
Tx prefix hash: b860b56e3cca7ebd1433dcd1ba8ba11042a1d0182734e70348bca4726d5482dd
Tx public key: 87cebec89d9f86ad3e0a7568a64707c27ae0e1e1708925f2eb8a000b1ea0782e
| Timestamp: 1779936682 | Timestamp [UTC]: 2026-05-28 02:51:22 | Age [y:d:h:m:s]: 00:011:22:44:35 |
| Block: 3445 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4441 | RingCT/type: yes/0 |
| Extra: 0187cebec89d9f86ad3e0a7568a64707c27ae0e1e1708925f2eb8a000b1ea0782e02090000000226697be300 | ||
1 output(s) for total of 34.954006395605 HMNY
| stealth address | amount | amount idx | tag |
| 00: 22baafa452543987f51053bcb502e65b87d6dd90ebe6d8f28d3daad07d5e5b56 | 34.954006395605 | 4162 of 0 | <1e> |
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": 3505,
"vin": [ {
"gen": {
"height": 3445
}
}
],
"vout": [ {
"amount": 34954006395605,
"target": {
"tagged_key": {
"key": "22baafa452543987f51053bcb502e65b87d6dd90ebe6d8f28d3daad07d5e5b56",
"view_tag": "1e"
}
}
}
],
"extra": [ 1, 135, 206, 190, 200, 157, 159, 134, 173, 62, 10, 117, 104, 166, 71, 7, 194, 122, 224, 225, 225, 112, 137, 37, 242, 235, 138, 0, 11, 30, 160, 120, 46, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}