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: 8a6379b534c5f97bd9a5af874d2624fb922db1437e9d1b2fb879fe7ab5903bb3
Tx prefix hash: 60536852283483d249e37fdf0a08c710181e110f2ff8eb839a7a29823692b985
Tx public key: d7d0e87b276d7f7df05d767c8d856bb22c823eb4b096585e3d8c4503bc166b06
| Timestamp: 1780754807 | Timestamp [UTC]: 2026-06-06 14:06:47 | Age [y:d:h:m:s]: 00:002:11:29:10 |
| Block: 6520 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1366 | RingCT/type: yes/0 |
| Extra: 01d7d0e87b276d7f7df05d767c8d856bb22c823eb4b096585e3d8c4503bc166b06020900000001e49593ff00 | ||
1 output(s) for total of 34.749597585727 HMNY
| stealth address | amount | amount idx | tag |
| 00: e59f362e1b08c2d7dc2eb505266616b33af976b8dc1cc714d8c2f08b70a9e109 | 34.749597585727 | 8020 of 0 | <da> |
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": 6580,
"vin": [ {
"gen": {
"height": 6520
}
}
],
"vout": [ {
"amount": 34749597585727,
"target": {
"tagged_key": {
"key": "e59f362e1b08c2d7dc2eb505266616b33af976b8dc1cc714d8c2f08b70a9e109",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 215, 208, 232, 123, 39, 109, 127, 125, 240, 93, 118, 124, 141, 133, 107, 178, 44, 130, 62, 180, 176, 150, 88, 94, 61, 140, 69, 3, 188, 22, 107, 6, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}