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: 3bfb3a33fa91a65ff2a8cdbe786e78202ddc03914e48d8b891f9b0a507bb253b
Tx prefix hash: da0c3bb830c3b65284098fb94a9cadf985f5c0b59dbda0f9e2e5cfefe0ac1586
Tx public key: 3dcde5fea49d0962cdc7ea0cbb9ec372bf7315a9a1a6eed1cd04a2e40656fb38
| Timestamp: 1779629362 | Timestamp [UTC]: 2026-05-24 13:29:22 | Age [y:d:h:m:s]: 00:015:12:06:35 |
| Block: 826 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7060 | RingCT/type: yes/0 |
| Extra: 013dcde5fea49d0962cdc7ea0cbb9ec372bf7315a9a1a6eed1cd04a2e40656fb38020900000001ba6d17be00 | ||
1 output(s) for total of 35.129050760589 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7388b4b514107af7d05fcd90d1424bc2d46a76b684eaf811a2b9e738f759fd38 | 35.129050760589 | 958 of 0 | <86> |
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": 886,
"vin": [ {
"gen": {
"height": 826
}
}
],
"vout": [ {
"amount": 35129050760589,
"target": {
"tagged_key": {
"key": "7388b4b514107af7d05fcd90d1424bc2d46a76b684eaf811a2b9e738f759fd38",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 61, 205, 229, 254, 164, 157, 9, 98, 205, 199, 234, 12, 187, 158, 195, 114, 191, 115, 21, 169, 161, 166, 238, 209, 205, 4, 162, 228, 6, 86, 251, 56, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}