Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3df7dea57095f812c4892d456b19f67dcc69919f929bda96a915be7adae48d33

Tx prefix hash: 68871d13793217764133501fd45fc336e6d22271c4458d5c811ca45cbeb1fab7
Tx public key: c548ad9f9a81059b212bbe5fea8288b8bf2b59e221ea715d65728b4fa7457070
Timestamp: 1755025846 Timestamp [UCT]: 2025-08-12 19:10:46 Age [y:d:h:m:s]: 00:099:22:14:09
Block: 1345636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70741 RingCT/type: yes/0
Extra: 01c548ad9f9a81059b212bbe5fea8288b8bf2b59e221ea715d65728b4fa7457070021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78542d7456a131507b68b9c1c491df0f87a265263040a4a4aa295d4318ab128f 0.600000000000 1833531 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": 1345646, "vin": [ { "gen": { "height": 1345636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78542d7456a131507b68b9c1c491df0f87a265263040a4a4aa295d4318ab128f" } } ], "extra": [ 1, 197, 72, 173, 159, 154, 129, 5, 155, 33, 43, 190, 95, 234, 130, 136, 184, 191, 43, 89, 226, 33, 234, 113, 93, 101, 114, 139, 79, 167, 69, 112, 112, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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