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: a6111754fec1969cca060c10462958d1f1147aa9d5d4b7083dcd8388c45556c9
Tx prefix hash: 672439f855de514bc1aaf6f5af3a2d1099336b0466e3bc2c7177c1c7a879e207
Tx public key: 95ee6ffce71ea6b61f995c3ee41325ab99821662dcf49544c52fb603bafddbc4
| Timestamp: 1780996485 | Timestamp [UTC]: 2026-06-09 09:14:45 | Age [y:d:h:m:s]: 00:009:22:26:52 |
| Block: 8348 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 397 | RingCT/type: yes/0 |
| Extra: 0195ee6ffce71ea6b61f995c3ee41325ab99821662dcf49544c52fb603bafddbc4020900000001e49593ff00 | ||
1 output(s) for total of 34.628649339868 HMNY
| stealth address | amount | amount idx | tag |
| 00: be1fee6efd3a9d1acf5dc595058674be301b3f71f7f3f0124cdd2ca54aa386a1 | 34.628649339868 | 10324 of 0 | <ac> |
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": 8408,
"vin": [ {
"gen": {
"height": 8348
}
}
],
"vout": [ {
"amount": 34628649339868,
"target": {
"tagged_key": {
"key": "be1fee6efd3a9d1acf5dc595058674be301b3f71f7f3f0124cdd2ca54aa386a1",
"view_tag": "ac"
}
}
}
],
"extra": [ 1, 149, 238, 111, 252, 231, 30, 166, 182, 31, 153, 92, 62, 228, 19, 37, 171, 153, 130, 22, 98, 220, 244, 149, 68, 197, 47, 182, 3, 186, 253, 219, 196, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}