Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: e33c0773d45d1e44f624ecdd86574c70dceea6bf36875c8c8fb509a0bc02694e

Tx prefix hash: 156f4887fd254233fc334fda59b1d5f615abec6517919535a80f51f6962ddc8d
Tx public key: d6af6a5e0c02db515645ba1eada511c53443bb401053eccc34c61aa6489e0e98
Timestamp: 1729638752 Timestamp [UCT]: 2024-10-22 23:12:32 Age [y:d:h:m:s]: 00:091:19:59:15
Block: 1137435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65614 RingCT/type: yes/0
Extra: 01d6af6a5e0c02db515645ba1eada511c53443bb401053eccc34c61aa6489e0e980211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d541a203341ed9f14133caa60a5e8c4333efd14f625c62479ab5280962b11f4 0.600000000000 1620926 of 15

Check which outputs belong to given Dinastycoin 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 Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-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": 1137445, "vin": [ { "gen": { "height": 1137435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d541a203341ed9f14133caa60a5e8c4333efd14f625c62479ab5280962b11f4" } } ], "extra": [ 1, 214, 175, 106, 94, 12, 2, 219, 81, 86, 69, 186, 30, 173, 165, 17, 197, 52, 67, 187, 64, 16, 83, 236, 204, 52, 198, 26, 166, 72, 158, 14, 152, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8