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: 64da4121c33d58ce2695ffc9307f4b1cf4b9f5fffa714d951306838a07bae62d
Tx prefix hash: 8cb71b924b27bb2bed30b85f6385d0c18acf37fb2b9de2a27a6e77662cd74c7f
Tx public key: faeeeccaaf3e0d11e2ec92dc1d6fb65c0dcca96c47f96804b13d307ef7ae7c1c
| Timestamp: 1780070512 | Timestamp [UTC]: 2026-05-29 16:01:52 | Age [y:d:h:m:s]: 00:010:09:34:05 |
| Block: 4637 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3249 | RingCT/type: yes/0 |
| Extra: 01faeeeccaaf3e0d11e2ec92dc1d6fb65c0dcca96c47f96804b13d307ef7ae7c1c02090000000526697be300 | ||
1 output(s) for total of 34.874626575709 HMNY
| stealth address | amount | amount idx | tag |
| 00: e88517016ce04eae1d4bfe696365ca86258c7ca9d388d963b9e2a8bdc0d464dd | 34.874626575709 | 5824 of 0 | <27> |
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": 4697,
"vin": [ {
"gen": {
"height": 4637
}
}
],
"vout": [ {
"amount": 34874626575709,
"target": {
"tagged_key": {
"key": "e88517016ce04eae1d4bfe696365ca86258c7ca9d388d963b9e2a8bdc0d464dd",
"view_tag": "27"
}
}
}
],
"extra": [ 1, 250, 238, 236, 202, 175, 62, 13, 17, 226, 236, 146, 220, 29, 111, 182, 92, 13, 204, 169, 108, 71, 249, 104, 4, 177, 61, 48, 126, 247, 174, 124, 28, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}