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: 8bbd016f0a5fcebfc38c0cbf49ddbf1986f1b843aca8bde4f7e3ce1eb144557a
Tx prefix hash: 6c743d494266d4c6f46a393934cba397af8ce155bef2227827cf9e197d577d0d
Tx public key: 6bee9ceea25b160085212de43f985dfde7a78540046764bedf69208294dae16c
| Timestamp: 1780996343 | Timestamp [UTC]: 2026-06-09 09:12:23 | Age [y:d:h:m:s]: 00:007:23:16:49 |
| Block: 8344 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 401 | RingCT/type: yes/0 |
| Extra: 016bee9ceea25b160085212de43f985dfde7a78540046764bedf69208294dae16c020900000001e49593ff00 | ||
1 output(s) for total of 34.628913536756 HMNY
| stealth address | amount | amount idx | tag |
| 00: e4b697fa468f11762e7efd9442b9ad5e6d9821b7261f5fb35c058fa7968411c3 | 34.628913536756 | 10320 of 0 | <8c> |
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": 8404,
"vin": [ {
"gen": {
"height": 8344
}
}
],
"vout": [ {
"amount": 34628913536756,
"target": {
"tagged_key": {
"key": "e4b697fa468f11762e7efd9442b9ad5e6d9821b7261f5fb35c058fa7968411c3",
"view_tag": "8c"
}
}
}
],
"extra": [ 1, 107, 238, 156, 238, 162, 91, 22, 0, 133, 33, 45, 228, 63, 152, 93, 253, 231, 167, 133, 64, 4, 103, 100, 190, 223, 105, 32, 130, 148, 218, 225, 108, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}