Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0bb52dca68a60fa827afa61107337df3d4fa7924bd46c72f7579133d3359eb1

Tx prefix hash: a26e65e20afb79dcf6af0b6c7f91eb48b17dde4194393f19cb9bcb89421520f4
Tx public key: dd46f382f135532531a5d46c8fc350e6ed06df20d236dc239faf0fdf22de4c74
Timestamp: 1763181776 Timestamp [UCT]: 2025-11-15 04:42:56 Age [y:d:h:m:s]: 00:038:09:07:51
Block: 1412424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27470 RingCT/type: yes/0
Extra: 01dd46f382f135532531a5d46c8fc350e6ed06df20d236dc239faf0fdf22de4c74021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2682f49f2bdb9ec73b5d769e2c9d548fea50cd38939383677569836b16c27635 0.600000000000 1900893 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": 1412434, "vin": [ { "gen": { "height": 1412424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2682f49f2bdb9ec73b5d769e2c9d548fea50cd38939383677569836b16c27635" } } ], "extra": [ 1, 221, 70, 243, 130, 241, 53, 83, 37, 49, 165, 212, 108, 143, 195, 80, 230, 237, 6, 223, 32, 210, 54, 220, 35, 159, 175, 15, 223, 34, 222, 76, 116, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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