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: 98a18878b3d14c06e7a772cc09c9366be4728596a821b651906579ac25f1b339
Tx prefix hash: cd1b23cb992bc6e72e9809727a478f4f8ae3f7fb6a3e942aa1aa68856302d43b
Tx public key: 0dcb977eb8d62a35acddc0d09181699ee36c96cd0ef374078486a8ff1a707a79
| Timestamp: 1780078685 | Timestamp [UTC]: 2026-05-29 18:18:05 | Age [y:d:h:m:s]: 00:010:08:22:31 |
| Block: 4732 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3165 | RingCT/type: yes/0 |
| Extra: 010dcb977eb8d62a35acddc0d09181699ee36c96cd0ef374078486a8ff1a707a7902090000000126697be300 | ||
1 output(s) for total of 34.868307925389 HMNY
| stealth address | amount | amount idx | tag |
| 00: afa2bd875167f33f45891f2a42e5fc071da49bf6667f505b4505c96685a392fa | 34.868307925389 | 5946 of 0 | <ba> |
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": 4792,
"vin": [ {
"gen": {
"height": 4732
}
}
],
"vout": [ {
"amount": 34868307925389,
"target": {
"tagged_key": {
"key": "afa2bd875167f33f45891f2a42e5fc071da49bf6667f505b4505c96685a392fa",
"view_tag": "ba"
}
}
}
],
"extra": [ 1, 13, 203, 151, 126, 184, 214, 42, 53, 172, 221, 192, 208, 145, 129, 105, 158, 227, 108, 150, 205, 14, 243, 116, 7, 132, 134, 168, 255, 26, 112, 122, 121, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}