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: 31c6f84b68cd69c023b583f331f004089a040ad53bd2bf31d29b943262e32121
Tx prefix hash: db8f8024e29c44c9e597a039e25757fc634f6b4cb8abf3d478363df7e789caa9
Tx public key: 0de95c5ae3025bf7789ca16528822e7413200b1ceee5a2636ea8df5b8ae28b75
| Timestamp: 1779945553 | Timestamp [UTC]: 2026-05-28 05:19:13 | Age [y:d:h:m:s]: 00:011:22:19:37 |
| Block: 3557 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4388 | RingCT/type: yes/0 |
| Extra: 010de95c5ae3025bf7789ca16528822e7413200b1ceee5a2636ea8df5b8ae28b7502090000000826697be300 | ||
1 output(s) for total of 34.949951804641 HMNY
| stealth address | amount | amount idx | tag |
| 00: d7656d6c09f2798a334956faf79430903b97008fc772ce9cdfe04249a9093e85 | 34.949951804641 | 4289 of 0 | <b2> |
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": 3617,
"vin": [ {
"gen": {
"height": 3557
}
}
],
"vout": [ {
"amount": 34949951804641,
"target": {
"tagged_key": {
"key": "d7656d6c09f2798a334956faf79430903b97008fc772ce9cdfe04249a9093e85",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 13, 233, 92, 90, 227, 2, 91, 247, 120, 156, 161, 101, 40, 130, 46, 116, 19, 32, 11, 28, 238, 229, 162, 99, 110, 168, 223, 91, 138, 226, 139, 117, 2, 9, 0, 0, 0, 8, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}