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: 439b4c368c05116a25a6a3dfd20837bf82fc30e81ba24a1892d7aee6dc070877
Tx prefix hash: dede2493495b6a2c01411c7e899faff47aada8b46bf5868ed2b062efb07bc2df
Tx public key: ded07e1cb3a538a66c1a2b2e782dab5ae4bc19e9ad03759a578783b49af1320c
| Timestamp: 1780737049 | Timestamp [UTC]: 2026-06-06 09:10:49 | Age [y:d:h:m:s]: 00:002:19:22:13 |
| Block: 6370 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1646 | RingCT/type: yes/0 |
| Extra: 01ded07e1cb3a538a66c1a2b2e782dab5ae4bc19e9ad03759a578783b49af1320c020900000001e49593ff00 | ||
1 output(s) for total of 34.759540957169 HMNY
| stealth address | amount | amount idx | tag |
| 00: d8a65640a02058a096e36751dfbc8410be70c7b01a16310b8e681d0f1f2c4b59 | 34.759540957169 | 7859 of 0 | <1b> |
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": 6430,
"vin": [ {
"gen": {
"height": 6370
}
}
],
"vout": [ {
"amount": 34759540957169,
"target": {
"tagged_key": {
"key": "d8a65640a02058a096e36751dfbc8410be70c7b01a16310b8e681d0f1f2c4b59",
"view_tag": "1b"
}
}
}
],
"extra": [ 1, 222, 208, 126, 28, 179, 165, 56, 166, 108, 26, 43, 46, 120, 45, 171, 90, 228, 188, 25, 233, 173, 3, 117, 154, 87, 135, 131, 180, 154, 241, 50, 12, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}