Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de6aa533b811dbb5dc348cd5bd98d02f43eaea8659cc1d97c731bf5848547d8f

Tx prefix hash: f95605f18e2b5d4dcadb01c3865f75b8c28c35e1e1212df609085e5002df6185
Tx public key: 88a3e00fdba29699835a4c26f80f1eb9b0151227ae9ef9f0be76031e907869f3
Timestamp: 1763049202 Timestamp [UCT]: 2025-11-13 15:53:22 Age [y:d:h:m:s]: 00:014:15:32:00
Block: 1411327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10488 RingCT/type: yes/0
Extra: 0188a3e00fdba29699835a4c26f80f1eb9b0151227ae9ef9f0be76031e907869f30211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d19173c296df7503b8b6256c96b79bed7057c5f498c9eab99295bc38056ee65 0.600000000000 1899788 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": 1411337, "vin": [ { "gen": { "height": 1411327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d19173c296df7503b8b6256c96b79bed7057c5f498c9eab99295bc38056ee65" } } ], "extra": [ 1, 136, 163, 224, 15, 219, 162, 150, 153, 131, 90, 76, 38, 248, 15, 30, 185, 176, 21, 18, 39, 174, 158, 249, 240, 190, 118, 3, 30, 144, 120, 105, 243, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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