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: 6ba1608bfc9e22a0647e5255603e9edb08eb1adcc434c2557c40f1113fc719a6
Tx prefix hash: b9e23c4556a3ea80c2e12e966c1023ee4890ff1bb2b4dc5466fa8df24d10531e
Tx public key: 6a9c558f7c67f30e9f073ce3126d986f6dc6a6c49eacdbd4cebdbdbfb1ae5be4
| Timestamp: 1780691371 | Timestamp [UTC]: 2026-06-05 20:29:31 | Age [y:d:h:m:s]: 00:003:07:21:27 |
| Block: 5723 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2243 | RingCT/type: yes/0 |
| Extra: 016a9c558f7c67f30e9f073ce3126d986f6dc6a6c49eacdbd4cebdbdbfb1ae5be4020900000001e49593ff00 | ||
1 output(s) for total of 34.836302646720 HMNY
| stealth address | amount | amount idx | tag |
| 00: 48613ae829d34cb453d2a65cf696497862685b5219fef65d23d8a904c539efce | 34.836302646720 | 7174 of 0 | <2b> |
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": 5783,
"vin": [ {
"gen": {
"height": 5723
}
}
],
"vout": [ {
"amount": 34836302646720,
"target": {
"tagged_key": {
"key": "48613ae829d34cb453d2a65cf696497862685b5219fef65d23d8a904c539efce",
"view_tag": "2b"
}
}
}
],
"extra": [ 1, 106, 156, 85, 143, 124, 103, 243, 14, 159, 7, 60, 227, 18, 109, 152, 111, 109, 198, 166, 196, 158, 172, 219, 212, 206, 189, 189, 191, 177, 174, 91, 228, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}