Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d487042e69f2ab423d40f934d122c3f4af048623cf355ecd2c70f2902323591

Tx prefix hash: 19334a4137a78bcdde4009fd8a7019b98d47d4cc3c329c88c77b2944fa6e6f91
Tx public key: 0efad22b6ddc4ccac67a903c26ab5798027ae8c4ed47d9ba2377ac2f68836063
Timestamp: 1745048565 Timestamp [UCT]: 2025-04-19 07:42:45 Age [y:d:h:m:s]: 00:264:22:17:17
Block: 1264714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187136 RingCT/type: yes/0
Extra: 010efad22b6ddc4ccac67a903c26ab5798027ae8c4ed47d9ba2377ac2f688360630211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 286f50fb33df5e79a97fea79fb8707b3fde8ea4e243b6eba10f684d0b3a2baa5 0.600000000000 1751915 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": 1264724, "vin": [ { "gen": { "height": 1264714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "286f50fb33df5e79a97fea79fb8707b3fde8ea4e243b6eba10f684d0b3a2baa5" } } ], "extra": [ 1, 14, 250, 210, 43, 109, 220, 76, 202, 198, 122, 144, 60, 38, 171, 87, 152, 2, 122, 232, 196, 237, 71, 217, 186, 35, 119, 172, 47, 104, 131, 96, 99, 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