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: e21ad5507648ecb859b2035328dd2d4f124e30669495f3994b78fc0c069c7462
Tx prefix hash: 69f3535c5e56a0bf3790205da43f22d250ae6b1e4e5efc58230db3327405a887
Tx public key: 7748bcd3dbfb9478c9c9fe1b1208870a6711065d5d439ce5bd6771b6ad46ba73
| Timestamp: 1779910498 | Timestamp [UTC]: 2026-05-27 19:34:58 | Age [y:d:h:m:s]: 00:012:06:00:59 |
| Block: 3241 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4645 | RingCT/type: yes/0 |
| Extra: 017748bcd3dbfb9478c9c9fe1b1208870a6711065d5d439ce5bd6771b6ad46ba7302090000000226697be300 | ||
1 output(s) for total of 34.967609628076 HMNY
| stealth address | amount | amount idx | tag |
| 00: d3c80322c1c0078f44c039a84382216f581a0968933f5fe246a6c12a6ea5d745 | 34.967609628076 | 3887 of 0 | <d5> |
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": 3301,
"vin": [ {
"gen": {
"height": 3241
}
}
],
"vout": [ {
"amount": 34967609628076,
"target": {
"tagged_key": {
"key": "d3c80322c1c0078f44c039a84382216f581a0968933f5fe246a6c12a6ea5d745",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 119, 72, 188, 211, 219, 251, 148, 120, 201, 201, 254, 27, 18, 8, 135, 10, 103, 17, 6, 93, 93, 67, 156, 229, 189, 103, 113, 182, 173, 70, 186, 115, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}