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: 0e8a29a1869675fdc33db9694e340fb795286f58de2cba826da5610a9dd5400b
Tx prefix hash: d3d249716d6cb706301a2cca1514fb799e0ebb38805ef8f8097e24647f49e040
Tx public key: 32245a6748e5beb3e9a9a4413313e02e9f878c959fcf535daca025cf7440662a
| Timestamp: 1780995278 | Timestamp [UTC]: 2026-06-09 08:54:38 | Age [y:d:h:m:s]: 00:000:04:42:58 |
| Block: 8318 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 280 | RingCT/type: yes/0 |
| Extra: 0132245a6748e5beb3e9a9a4413313e02e9f878c959fcf535daca025cf7440662a020900000003e49593ff00 | ||
1 output(s) for total of 34.630630865658 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1515671a0c2499df17ed842338cc3d88250832114c151cb9ac420e5b9d58abdf | 34.630630865658 | 10290 of 0 | <91> |
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": 8378,
"vin": [ {
"gen": {
"height": 8318
}
}
],
"vout": [ {
"amount": 34630630865658,
"target": {
"tagged_key": {
"key": "1515671a0c2499df17ed842338cc3d88250832114c151cb9ac420e5b9d58abdf",
"view_tag": "91"
}
}
}
],
"extra": [ 1, 50, 36, 90, 103, 72, 229, 190, 179, 233, 169, 164, 65, 51, 19, 224, 46, 159, 135, 140, 149, 159, 207, 83, 93, 172, 160, 37, 207, 116, 64, 102, 42, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}