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: dfa1a585777c1afa790100b7c095d0bfc594351e42f62f271793b203014b3c3e
Tx prefix hash: 83b68c52bf16638451f6fe47685da6ac42df7fe18cc245fa87480753c4ea0528
Tx public key: 1ecd1e99c7a644b9b0e0c954952173dc20b4bd5b9e4ef6f7acb51f78cb837daf
| Timestamp: 1780689788 | Timestamp [UTC]: 2026-06-05 20:03:08 | Age [y:d:h:m:s]: 00:003:07:35:42 |
| Block: 5621 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2329 | RingCT/type: yes/0 |
| Extra: 011ecd1e99c7a644b9b0e0c954952173dc20b4bd5b9e4ef6f7acb51f78cb837daf020900000001e49593ff00 | ||
1 output(s) for total of 34.809234115663 HMNY
| stealth address | amount | amount idx | tag |
| 00: 69e29b16ebf33cc09fc0a89406022d8615db016a04b31fe952ef782f0ee208cb | 34.809234115663 | 7068 of 0 | <96> |
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": 5681,
"vin": [ {
"gen": {
"height": 5621
}
}
],
"vout": [ {
"amount": 34809234115663,
"target": {
"tagged_key": {
"key": "69e29b16ebf33cc09fc0a89406022d8615db016a04b31fe952ef782f0ee208cb",
"view_tag": "96"
}
}
}
],
"extra": [ 1, 30, 205, 30, 153, 199, 166, 68, 185, 176, 224, 201, 84, 149, 33, 115, 220, 32, 180, 189, 91, 158, 78, 246, 247, 172, 181, 31, 120, 203, 131, 125, 175, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}