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: f3d0268ed767e40b2f2b1528e036e627c9e39d8b1b7f6ed8e023dd85eaa7716e
Tx prefix hash: 7babecf4a2fff039aa730c72bb9f1b1669c8d632639e16f12db8ca6ee156b0a5
Tx public key: 1aaa3240f03999da9f814ddb0d232f42c78de162db9fd34bf2d568db541f0c40
| Timestamp: 1779447851 | Timestamp [UTC]: 2026-05-22 11:04:11 | Age [y:d:h:m:s]: 00:017:15:36:25 |
| Block: 292 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7604 | RingCT/type: yes/0 |
| Extra: 011aaa3240f03999da9f814ddb0d232f42c78de162db9fd34bf2d568db541f0c400209000000014438f87f00 | ||
1 output(s) for total of 35.164848809489 HMNY
| stealth address | amount | amount idx | tag |
| 00: 343d15fbd5661fc6c6a66deb2a28862a9a7f363270945a43cd4d1ff0191a44a5 | 35.164848809489 | 288 of 0 | <db> |
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": 352,
"vin": [ {
"gen": {
"height": 292
}
}
],
"vout": [ {
"amount": 35164848809489,
"target": {
"tagged_key": {
"key": "343d15fbd5661fc6c6a66deb2a28862a9a7f363270945a43cd4d1ff0191a44a5",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 26, 170, 50, 64, 240, 57, 153, 218, 159, 129, 77, 219, 13, 35, 47, 66, 199, 141, 225, 98, 219, 159, 211, 75, 242, 213, 104, 219, 84, 31, 12, 64, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}