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: c4fbd5893e0072b1d13c5fe76b21079124f5ffaf2b4c0e9b80b9fe6f4dc822cd
Tx prefix hash: 4146f3bcfdc1276e32a0f397f12221094cf0c901e691b7b2da007de83b61fd0d
Tx public key: 219339760abcc166a0f82cd9cbbe18babec1539bc3ab7916dbb0c1ef69e41076
| Timestamp: 1780754314 | Timestamp [UTC]: 2026-06-06 13:58:34 | Age [y:d:h:m:s]: 00:006:21:03:42 |
| Block: 6518 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2227 | RingCT/type: yes/0 |
| Extra: 01219339760abcc166a0f82cd9cbbe18babec1539bc3ab7916dbb0c1ef69e41076020900000006e49593ff00 | ||
1 output(s) for total of 34.749730145301 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3eb0c7d24be9081c60c36f0c91b62e2a8424059cd75f13fd655f354fbbb00e19 | 34.749730145301 | 8015 of 0 | <e9> |
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": 6578,
"vin": [ {
"gen": {
"height": 6518
}
}
],
"vout": [ {
"amount": 34749730145301,
"target": {
"tagged_key": {
"key": "3eb0c7d24be9081c60c36f0c91b62e2a8424059cd75f13fd655f354fbbb00e19",
"view_tag": "e9"
}
}
}
],
"extra": [ 1, 33, 147, 57, 118, 10, 188, 193, 102, 160, 248, 44, 217, 203, 190, 24, 186, 190, 193, 83, 155, 195, 171, 121, 22, 219, 176, 193, 239, 105, 228, 16, 118, 2, 9, 0, 0, 0, 6, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}