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: 7afefdcf8d03b38e71b68d4dd2e0ed9324de63e2a8984054d5cbb2c51af3287d
Tx prefix hash: a5ca3a4d6259e43c2d4b460019df629d3a8311774f24c972e315bef86cba0835
Tx public key: 5823493f5e20a5047fd5f1a345e2a72a93b52c7bb3cf1d2f9d2421e775899f62
| Timestamp: 1779959483 | Timestamp [UTC]: 2026-05-28 09:11:23 | Age [y:d:h:m:s]: 00:016:01:50:53 |
| Block: 3736 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5009 | RingCT/type: yes/0 |
| Extra: 015823493f5e20a5047fd5f1a345e2a72a93b52c7bb3cf1d2f9d2421e775899f6202090000000326697be300 | ||
1 output(s) for total of 34.934610942611 HMNY
| stealth address | amount | amount idx | tag |
| 00: c6411923637b1e299421c9e26abce86d62cfeea30d62023993bae324ced08182 | 34.934610942611 | 4528 of 0 | <ea> |
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": 3796,
"vin": [ {
"gen": {
"height": 3736
}
}
],
"vout": [ {
"amount": 34934610942611,
"target": {
"tagged_key": {
"key": "c6411923637b1e299421c9e26abce86d62cfeea30d62023993bae324ced08182",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 88, 35, 73, 63, 94, 32, 165, 4, 127, 213, 241, 163, 69, 226, 167, 42, 147, 181, 44, 123, 179, 207, 29, 47, 157, 36, 33, 231, 117, 137, 159, 98, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}