Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4659260ff07a3f98a19b047b3942d19d7d01df1698ba22aa9d3cb07fa8a93cc

Tx prefix hash: dd41816978b590ff0cc9a32cb06eadc05a1d8ef238d23be346716750697c52f1
Tx public key: 104181293ea6b1d5a3654bbade0653a1c3c6b6544143d05b479cc3b49eb9a09f
Timestamp: 1765467038 Timestamp [UCT]: 2025-12-11 15:30:38 Age [y:d:h:m:s]: 00:047:09:35:12
Block: 1431367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33753 RingCT/type: yes/0
Extra: 01104181293ea6b1d5a3654bbade0653a1c3c6b6544143d05b479cc3b49eb9a09f0211000000048ceb7f09000000000000000000

1 output(s) for total of 0.600030000000 dcy

stealth address amount amount idx
00: 234bdb38eb015b28ebf8a81e911a9903b0c077accab1500125a92e4be47b87ed 0.600030000000 1920126 of 0

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": 1431377, "vin": [ { "gen": { "height": 1431367 } } ], "vout": [ { "amount": 600030000, "target": { "key": "234bdb38eb015b28ebf8a81e911a9903b0c077accab1500125a92e4be47b87ed" } } ], "extra": [ 1, 16, 65, 129, 41, 62, 166, 177, 213, 163, 101, 75, 186, 222, 6, 83, 161, 195, 198, 182, 84, 65, 67, 208, 91, 71, 156, 195, 180, 158, 185, 160, 159, 2, 17, 0, 0, 0, 4, 140, 235, 127, 9, 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