Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c67faa2b29b99302b0602cd14847b3a317d62369933f63df7e584d3791dae573

Tx prefix hash: 8e05657cd27b837bec7107810f2f695af6375f13adc5bf7cb099a9c2b9a5b656
Tx public key: 005d74e9560b8b9f2d78c91ed369c067f795fecba0de94eb2286d4b9ab7c1587
Timestamp: 1728346656 Timestamp [UCT]: 2024-10-08 00:17:36 Age [y:d:h:m:s]: 00:113:05:28:26
Block: 1126763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80681 RingCT/type: yes/0
Extra: 01005d74e9560b8b9f2d78c91ed369c067f795fecba0de94eb2286d4b9ab7c158702110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06b935807fad7d2f2146c3cdd5c9205eafe5b1c5daa39cca5d90f1344d628274 0.600000000000 1609558 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": 1126773, "vin": [ { "gen": { "height": 1126763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06b935807fad7d2f2146c3cdd5c9205eafe5b1c5daa39cca5d90f1344d628274" } } ], "extra": [ 1, 0, 93, 116, 233, 86, 11, 139, 159, 45, 120, 201, 30, 211, 105, 192, 103, 247, 149, 254, 203, 160, 222, 148, 235, 34, 134, 212, 185, 171, 124, 21, 135, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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