Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d608f6b18913fd0843322402c5c383f2be42b8b8f48f33ab42cef8388a80263

Tx prefix hash: 22306c78c101a71986f7e702d0bb90b78e36545cbad720774e4dcab6d3f98642
Tx public key: 1dd70ab47ba3dde8ec988f23cb2b03398dc5a169efd9dffc3420a263ae0b0b81
Timestamp: 1765919988 Timestamp [UCT]: 2025-12-16 21:19:48 Age [y:d:h:m:s]: 00:005:15:22:31
Block: 1435112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4045 RingCT/type: yes/0
Extra: 011dd70ab47ba3dde8ec988f23cb2b03398dc5a169efd9dffc3420a263ae0b0b81021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66f4100f504cfac30e4a80a6f0062ac8a8d6057830e9f562ca8a5b84fa78f12f 0.600000000000 1923909 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": 1435122, "vin": [ { "gen": { "height": 1435112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66f4100f504cfac30e4a80a6f0062ac8a8d6057830e9f562ca8a5b84fa78f12f" } } ], "extra": [ 1, 29, 215, 10, 180, 123, 163, 221, 232, 236, 152, 143, 35, 203, 43, 3, 57, 141, 197, 161, 105, 239, 217, 223, 252, 52, 32, 162, 99, 174, 11, 11, 129, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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