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: 0aa1ec0616f707d41dcdd6cdf8b87b7ebcff6109f283576451090c2110335a11
Tx prefix hash: b04a521c1f3efd658f161685274e2a2a067a6d96e992e3e8b67b63f44baa8e82
Tx public key: b0deaece0d29824c1eef8de6cd2955c49cf520af2b6d2802102093bdfc29f20c
| Timestamp: 1780738191 | Timestamp [UTC]: 2026-06-06 09:29:51 | Age [y:d:h:m:s]: 00:002:15:16:56 |
| Block: 6386 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1500 | RingCT/type: yes/0 |
| Extra: 01b0deaece0d29824c1eef8de6cd2955c49cf520af2b6d2802102093bdfc29f20c020900000004e49593ff00 | ||
1 output(s) for total of 34.758480195337 HMNY
| stealth address | amount | amount idx | tag |
| 00: c70aefb249da0138ad24a4933d9e377e830c4e7ab25810c1e080746a831987ae | 34.758480195337 | 7875 of 0 | <af> |
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": 6446,
"vin": [ {
"gen": {
"height": 6386
}
}
],
"vout": [ {
"amount": 34758480195337,
"target": {
"tagged_key": {
"key": "c70aefb249da0138ad24a4933d9e377e830c4e7ab25810c1e080746a831987ae",
"view_tag": "af"
}
}
}
],
"extra": [ 1, 176, 222, 174, 206, 13, 41, 130, 76, 30, 239, 141, 230, 205, 41, 85, 196, 156, 245, 32, 175, 43, 109, 40, 2, 16, 32, 147, 189, 252, 41, 242, 12, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}