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: 2e6a736def3b3c6719d605011c6ba5d2c1259d93e0e2a9eb2353bc2df1052aa9
Tx prefix hash: 5e616452ad05859ccdf67ec9c02d822003f5967021b7eef3631ac9144678fb45
Tx public key: 18a0df20bb77ccc4325e98a35ceb8bcb2b558f8e265a8b4d4ec4649b7c0fef1d
| Timestamp: 1780833807 | Timestamp [UTC]: 2026-06-07 12:03:27 | Age [y:d:h:m:s]: 00:001:12:43:20 |
| Block: 7376 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 510 | RingCT/type: yes/0 |
| Extra: 0118a0df20bb77ccc4325e98a35ceb8bcb2b558f8e265a8b4d4ec4649b7c0fef1d020900000001e49593ff00 | ||
1 output(s) for total of 34.692908486718 HMNY
| stealth address | amount | amount idx | tag |
| 00: db1633ea9b349d12d5e70634b28c50625a291a27c47510394bb08c37e9d81cb8 | 34.692908486718 | 9082 of 0 | <8a> |
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": 7436,
"vin": [ {
"gen": {
"height": 7376
}
}
],
"vout": [ {
"amount": 34692908486718,
"target": {
"tagged_key": {
"key": "db1633ea9b349d12d5e70634b28c50625a291a27c47510394bb08c37e9d81cb8",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 24, 160, 223, 32, 187, 119, 204, 196, 50, 94, 152, 163, 92, 235, 139, 203, 43, 85, 143, 142, 38, 90, 139, 77, 78, 196, 100, 155, 124, 15, 239, 29, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}