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: ad70b1a22e6a3c9b75414ffd6bfbd172f7872c8892ea3843519c763c29374086
Tx prefix hash: d1eba94e8b80c19f5b8e702729057b4e60efb94b76e0fdd2eb8fa2409c5deb8e
Tx public key: b09bd6168561a7ebfc0a19a1e57c4fef9cc53300e2d346aade56aa25142f08a9
| Timestamp: 1779714945 | Timestamp [UTC]: 2026-05-25 13:15:45 | Age [y:d:h:m:s]: 00:014:15:17:17 |
| Block: 1624 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6406 | RingCT/type: yes/0 |
| Extra: 01b09bd6168561a7ebfc0a19a1e57c4fef9cc53300e2d346aade56aa25142f08a9020900000003ba6d17be00 | ||
1 output(s) for total of 35.075622709554 HMNY
| stealth address | amount | amount idx | tag |
| 00: 425872827e4dc11776df60b4841328efd3bb87aafb2a72dc8deca8e3f2a99324 | 35.075622709554 | 1782 of 0 | <be> |
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": 1684,
"vin": [ {
"gen": {
"height": 1624
}
}
],
"vout": [ {
"amount": 35075622709554,
"target": {
"tagged_key": {
"key": "425872827e4dc11776df60b4841328efd3bb87aafb2a72dc8deca8e3f2a99324",
"view_tag": "be"
}
}
}
],
"extra": [ 1, 176, 155, 214, 22, 133, 97, 167, 235, 252, 10, 25, 161, 229, 124, 79, 239, 156, 197, 51, 0, 226, 211, 70, 170, 222, 86, 170, 37, 20, 47, 8, 169, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}