Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68323afd3fb7004a12a8ff6c40418a5fe05a70800c7686bdf9b470208d5dad94

Tx prefix hash: c68e870dddf05604fccfc3b22071c7b0b7787deb49def77cfe386fdc1e3f9bf2
Tx public key: c8dda0afcd5cf8da724a73dc2657dacd16c7f5c1f2701bbeb9f6335483d7fa65
Timestamp: 1735883534 Timestamp [UCT]: 2025-01-03 05:52:14 Age [y:d:h:m:s]: 00:167:03:05:48
Block: 1189120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119123 RingCT/type: yes/0
Extra: 01c8dda0afcd5cf8da724a73dc2657dacd16c7f5c1f2701bbeb9f6335483d7fa65021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db6f04309f3124ad568cafc37ff6ef7d6a78ec545a3ca7eecf49a6f82c0ea9b2 0.600000000000 1675625 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": 1189130, "vin": [ { "gen": { "height": 1189120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db6f04309f3124ad568cafc37ff6ef7d6a78ec545a3ca7eecf49a6f82c0ea9b2" } } ], "extra": [ 1, 200, 221, 160, 175, 205, 92, 248, 218, 114, 74, 115, 220, 38, 87, 218, 205, 22, 199, 245, 193, 242, 112, 27, 190, 185, 246, 51, 84, 131, 215, 250, 101, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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