Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec7bc9f2e29241cd298e6f2ec55313f40fa50f14d4d3e5b194e767a5039edbea

Tx prefix hash: 723b1b94a8b6959e640b811b6dde5e3844c1232226245e047d5f0617b8da84eb
Tx public key: cf9188f02ecbe695c7ef4d20d3956b9ff0efa7d017d76d03615b2bf9af959353
Timestamp: 1753899936 Timestamp [UCT]: 2025-07-30 18:25:36 Age [y:d:h:m:s]: 00:070:05:31:18
Block: 1336811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48979 RingCT/type: yes/0
Extra: 01cf9188f02ecbe695c7ef4d20d3956b9ff0efa7d017d76d03615b2bf9af959353021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 227aa8b5f14b3ea7d1dd98cc3755bc85f850220b93552125e62fe930918fa084 0.600000000000 1824614 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": 1336821, "vin": [ { "gen": { "height": 1336811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "227aa8b5f14b3ea7d1dd98cc3755bc85f850220b93552125e62fe930918fa084" } } ], "extra": [ 1, 207, 145, 136, 240, 46, 203, 230, 149, 199, 239, 77, 32, 211, 149, 107, 159, 240, 239, 167, 208, 23, 215, 109, 3, 97, 91, 43, 249, 175, 149, 147, 83, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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