Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bb01596c910bcd9a2b43e076113451833f92959c13ded8b9a26d6ed2529b0ad

Tx prefix hash: 0326c540448df7694ea53b1a05305b1b9903719340e4001e6dccd6dc4a89d169
Tx public key: 3cf735d7df16d2476459e8b56f3ef63dd7d9a99582e60c17aae62c08da3f7d73
Timestamp: 1763182247 Timestamp [UCT]: 2025-11-15 04:50:47 Age [y:d:h:m:s]: 00:051:19:37:13
Block: 1412427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37128 RingCT/type: yes/0
Extra: 013cf735d7df16d2476459e8b56f3ef63dd7d9a99582e60c17aae62c08da3f7d7302110000000601491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 572b25026906c43ada278d71e524c4886e89498eb979c1b2d29d3518e8bc9bcb 0.600000000000 1900896 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": 1412437, "vin": [ { "gen": { "height": 1412427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "572b25026906c43ada278d71e524c4886e89498eb979c1b2d29d3518e8bc9bcb" } } ], "extra": [ 1, 60, 247, 53, 215, 223, 22, 210, 71, 100, 89, 232, 181, 111, 62, 246, 61, 215, 217, 169, 149, 130, 230, 12, 23, 170, 230, 44, 8, 218, 63, 125, 115, 2, 17, 0, 0, 0, 6, 1, 73, 31, 136, 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