Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1568e3bff415e9afc8dca81b3d5444422cde4865216abb5627c7c5b67af3370

Tx prefix hash: fd9fa6b3d73340b6e866fee33948bfeca2bc18988c0dea261943265030219464
Tx public key: d89ac1d7d2400e9f17b5465ef31c8c8d4e454f7841e4c5e84a7c8371c68a834a
Timestamp: 1762052855 Timestamp [UCT]: 2025-11-02 03:07:35 Age [y:d:h:m:s]: 00:006:00:30:17
Block: 1403072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4310 RingCT/type: yes/0
Extra: 01d89ac1d7d2400e9f17b5465ef31c8c8d4e454f7841e4c5e84a7c8371c68a834a021100000005df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd4821fe101970f95fedd58e283f0b554f21bb48a1d3888779c6a84467cdc2c0 0.600000000000 1891399 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": 1403082, "vin": [ { "gen": { "height": 1403072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd4821fe101970f95fedd58e283f0b554f21bb48a1d3888779c6a84467cdc2c0" } } ], "extra": [ 1, 216, 154, 193, 215, 210, 64, 14, 159, 23, 181, 70, 94, 243, 28, 140, 141, 78, 69, 79, 120, 65, 228, 197, 232, 74, 124, 131, 113, 198, 138, 131, 74, 2, 17, 0, 0, 0, 5, 223, 90, 36, 122, 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