Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c28e57080d31952f766c7a8d983e30ec1a52ac692e503ffcf35aa2333d5c90f6

Tx prefix hash: 6ea368d63934d5dcd323eb9e5a5921f5eec7ab613dd3212aecc5a34feff7d2ed
Tx public key: 328707f18fa2f359f0dfecf1b7f165325a87d80c12f271fa296e9375576f3eeb
Timestamp: 1745497503 Timestamp [UCT]: 2025-04-24 12:25:03 Age [y:d:h:m:s]: 00:210:02:05:06
Block: 1268430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147858 RingCT/type: yes/0
Extra: 01328707f18fa2f359f0dfecf1b7f165325a87d80c12f271fa296e9375576f3eeb0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7028d962e0ee89d80597523d607ba416689d1c69fecda954fdb6f39b160bef84 0.600000000000 1755659 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": 1268440, "vin": [ { "gen": { "height": 1268430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7028d962e0ee89d80597523d607ba416689d1c69fecda954fdb6f39b160bef84" } } ], "extra": [ 1, 50, 135, 7, 241, 143, 162, 243, 89, 240, 223, 236, 241, 183, 241, 101, 50, 90, 135, 216, 12, 18, 242, 113, 250, 41, 110, 147, 117, 87, 111, 62, 235, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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