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: e0af22bd3eaafc18c5d806c564589f859c7cae6937e93176a7e90fbec3b088c2
Tx prefix hash: 76904cda1f10e2fa6aee6ecd145c80113a2449dc59e597a1221d4105a7777622
Tx public key: 2ac38b128c8bf98a54d719d4c2cb410c744196f3dd5f39d3753d31743b9c2db3
| Timestamp: 1780770991 | Timestamp [UTC]: 2026-06-06 18:36:31 | Age [y:d:h:m:s]: 00:002:08:13:17 |
| Block: 6664 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1256 | RingCT/type: yes/0 |
| Extra: 012ac38b128c8bf98a54d719d4c2cb410c744196f3dd5f39d3753d31743b9c2db3020900000001e49593ff00 | ||
1 output(s) for total of 34.740054625180 HMNY
| stealth address | amount | amount idx | tag |
| 00: ef1955ba36ed36ab4abbdc765cf3a3a4931e43de90be33e60b2f38734400e3b1 | 34.740054625180 | 8218 of 0 | <e3> |
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": 6724,
"vin": [ {
"gen": {
"height": 6664
}
}
],
"vout": [ {
"amount": 34740054625180,
"target": {
"tagged_key": {
"key": "ef1955ba36ed36ab4abbdc765cf3a3a4931e43de90be33e60b2f38734400e3b1",
"view_tag": "e3"
}
}
}
],
"extra": [ 1, 42, 195, 139, 18, 140, 139, 249, 138, 84, 215, 25, 212, 194, 203, 65, 12, 116, 65, 150, 243, 221, 95, 57, 211, 117, 61, 49, 116, 59, 156, 45, 179, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}