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: b4f3e2005b2e81709e5832f0267bd109d21410643b6c4d9dd59ff27291aa9e49
Tx prefix hash: c086e449dd4dce6854b7a4a5294344cf5339ccb229fd22097b2a283eab186237
Tx public key: dd06e64c1e558dc884677c2ba6f36b21c6cef0cf8cb4a18f11f95439aed22f9d
| Timestamp: 1780988084 | Timestamp [UTC]: 2026-06-09 06:54:44 | Age [y:d:h:m:s]: 00:000:09:05:00 |
| Block: 8179 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 512 | RingCT/type: yes/0 |
| Extra: 01dd06e64c1e558dc884677c2ba6f36b21c6cef0cf8cb4a18f11f95439aed22f9d020900000001e49593ff00 | ||
1 output(s) for total of 34.639813415022 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1aeae20a6536bc09e00bb1e1c79b1b644786ab00e7f8b6f2fb14da76b1e6c882 | 34.639813415022 | 10127 of 0 | <31> |
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": 8239,
"vin": [ {
"gen": {
"height": 8179
}
}
],
"vout": [ {
"amount": 34639813415022,
"target": {
"tagged_key": {
"key": "1aeae20a6536bc09e00bb1e1c79b1b644786ab00e7f8b6f2fb14da76b1e6c882",
"view_tag": "31"
}
}
}
],
"extra": [ 1, 221, 6, 230, 76, 30, 85, 141, 200, 132, 103, 124, 43, 166, 243, 107, 33, 198, 206, 240, 207, 140, 180, 161, 143, 17, 249, 84, 57, 174, 210, 47, 157, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}