Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6bdd5f0d658a15076ed9a0e96421db7afa41ba93655518b8045c5c3b8742fa8

Tx prefix hash: 1b5f64ff9c7c291b7782d19ea11205abeedcc02cc9b186cb8dd5870a3490b17a
Tx public key: bc940763e19d95bd2c416c0e388d1ffc92980a200b11de24464e2a709fe060b8
Timestamp: 1713941349 Timestamp [UCT]: 2024-04-24 06:49:09 Age [y:d:h:m:s]: 00:205:03:48:35
Block: 1007330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146862 RingCT/type: yes/0
Extra: 01bc940763e19d95bd2c416c0e388d1ffc92980a200b11de24464e2a709fe060b802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6df4c19aad7b4aca8e22500c513c4fd32b48b874cf84957559a2b1ce4eb20b8d 0.600000000000 1468634 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": 1007340, "vin": [ { "gen": { "height": 1007330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6df4c19aad7b4aca8e22500c513c4fd32b48b874cf84957559a2b1ce4eb20b8d" } } ], "extra": [ 1, 188, 148, 7, 99, 225, 157, 149, 189, 44, 65, 108, 14, 56, 141, 31, 252, 146, 152, 10, 32, 11, 17, 222, 36, 70, 78, 42, 112, 159, 224, 96, 184, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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