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: 7353567be67e7d88d9242873112cbfa4a2f7101f6a3f6dcd121eedcf76cc7c56
Tx prefix hash: 8b1eaa6a07b9c5a3b7e25e0620a282b6955ba046e31436120f6b87186004f12d
Tx public key: 75dfdd44d1cc017fa861809f352b8b27f028d9b5cfd7a04784e7b3410e61444f
| Timestamp: 1780797986 | Timestamp [UTC]: 2026-06-07 02:06:26 | Age [y:d:h:m:s]: 00:001:22:40:21 |
| Block: 6788 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1098 | RingCT/type: yes/0 |
| Extra: 0175dfdd44d1cc017fa861809f352b8b27f028d9b5cfd7a04784e7b3410e61444f020900000001e49593ff00 | ||
1 output(s) for total of 34.731839175840 HMNY
| stealth address | amount | amount idx | tag |
| 00: bdbea007cfbe9854e95c61a18ea2e6d39443301316bfee250d73cc3b715ca155 | 34.731839175840 | 8382 of 0 | <92> |
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": 6848,
"vin": [ {
"gen": {
"height": 6788
}
}
],
"vout": [ {
"amount": 34731839175840,
"target": {
"tagged_key": {
"key": "bdbea007cfbe9854e95c61a18ea2e6d39443301316bfee250d73cc3b715ca155",
"view_tag": "92"
}
}
}
],
"extra": [ 1, 117, 223, 221, 68, 209, 204, 1, 127, 168, 97, 128, 159, 53, 43, 139, 39, 240, 40, 217, 181, 207, 215, 160, 71, 132, 231, 179, 65, 14, 97, 68, 79, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}