Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3333d79eea934a0ebf68a64b2ce782997888fce04b52503e2a95c99a33b50035

Tx prefix hash: 8c18df0876d63c8ba66fcd132eafae18aea960f917e72cc40ada80fc3d539bc7
Tx public key: c66793b739feb6fd872fc26e475ee1aa95fa7778c8d4aba7cfa1fdeca71a0975
Timestamp: 1735234787 Timestamp [UCT]: 2024-12-26 17:39:47 Age [y:d:h:m:s]: 00:090:08:27:40
Block: 1183732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64342 RingCT/type: yes/0
Extra: 01c66793b739feb6fd872fc26e475ee1aa95fa7778c8d4aba7cfa1fdeca71a09750211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23f2ea6c05b2adf5635aceea95c3deb8d00d25a363afebe34a6b4f6d3a309b82 0.600000000000 1670181 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": 1183742, "vin": [ { "gen": { "height": 1183732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23f2ea6c05b2adf5635aceea95c3deb8d00d25a363afebe34a6b4f6d3a309b82" } } ], "extra": [ 1, 198, 103, 147, 183, 57, 254, 182, 253, 135, 47, 194, 110, 71, 94, 225, 170, 149, 250, 119, 120, 200, 212, 171, 167, 207, 161, 253, 236, 167, 26, 9, 117, 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