Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5620e291d65635bb7598d297c9f330f4b714a3aefed0cf60864a9a37661d5587

Tx prefix hash: 10b87ebce61eae6eeef0ee7d0149848ebb3085c48946e467449be6a593189d17
Tx public key: 600853c41991d8c00fbae8f8a3096e745e96cb387bdee8c8d03d6ae5556354a2
Timestamp: 1628881429 Timestamp [UCT]: 2021-08-13 19:03:49 Age [y:d:h:m:s]: 03:299:22:37:14
Block: 313362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 987419 RingCT/type: yes/0
Extra: 01600853c41991d8c00fbae8f8a3096e745e96cb387bdee8c8d03d6ae5556354a2021100000019e6f80b5a000000000000000000

1 output(s) for total of 56.195570191000 dcy

stealth address amount amount idx
00: a5ab2a9069c3701ff0b60a0b2b0025003225bb813b4d4bdcaaf4eb0233428600 56.195570191000 652123 of 0

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": 313372, "vin": [ { "gen": { "height": 313362 } } ], "vout": [ { "amount": 56195570191, "target": { "key": "a5ab2a9069c3701ff0b60a0b2b0025003225bb813b4d4bdcaaf4eb0233428600" } } ], "extra": [ 1, 96, 8, 83, 196, 25, 145, 216, 192, 15, 186, 232, 248, 163, 9, 110, 116, 94, 150, 203, 56, 123, 222, 232, 200, 208, 61, 106, 229, 85, 99, 84, 162, 2, 17, 0, 0, 0, 25, 230, 248, 11, 90, 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