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: 3eb615fb1206a6d4d3cf2dda7dd5f583d7c1dd775715abdc7fdc94e9add2d3c3
Tx prefix hash: b0d4d822ba84aae6fa5039b05210950a832e78f09b790e1f5fc0fdd727a82ca6
Tx public key: 2d136abd5444eeb45f9b8ba8e4a198b9b91b8e2d0c38716ee0a75a57955dd13b
| Timestamp: 1780709307 | Timestamp [UTC]: 2026-06-06 01:28:27 | Age [y:d:h:m:s]: 00:002:21:50:26 |
| Block: 6148 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1738 | RingCT/type: yes/0 |
| Extra: 012d136abd5444eeb45f9b8ba8e4a198b9b91b8e2d0c38716ee0a75a57955dd13b020900000001e49593ff00 | ||
1 output(s) for total of 34.774262368711 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3b778db70ec834c92ca63c460c6b13a10ff6c24323688eef94040cefbf5c39d4 | 34.774262368711 | 7623 of 0 | <52> |
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": 6208,
"vin": [ {
"gen": {
"height": 6148
}
}
],
"vout": [ {
"amount": 34774262368711,
"target": {
"tagged_key": {
"key": "3b778db70ec834c92ca63c460c6b13a10ff6c24323688eef94040cefbf5c39d4",
"view_tag": "52"
}
}
}
],
"extra": [ 1, 45, 19, 106, 189, 84, 68, 238, 180, 95, 155, 139, 168, 228, 161, 152, 185, 185, 27, 142, 45, 12, 56, 113, 110, 224, 167, 90, 87, 149, 93, 209, 59, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}