Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3c1dd64f9942f8b2e29e185eb9227f0a210bbacbf1325680f4bed06c5ead63c

Tx prefix hash: 68417d8c79094c0012e0626648f375f833ce71b91822097e6871f31994b87fbf
Tx public key: 0f1fdd5495b7d2e7a18e20f2483e5e37e150594644fee7d8a385503a3c067514
Timestamp: 1763878324 Timestamp [UCT]: 2025-11-23 06:12:04 Age [y:d:h:m:s]: 00:003:09:00:16
Block: 1418200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2417 RingCT/type: yes/0
Extra: 010f1fdd5495b7d2e7a18e20f2483e5e37e150594644fee7d8a385503a3c0675140211000000068ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96574efdf99c850d835a1a953a3d589dc3f0e917c7ca728055c72f2ae6ccf81f 0.600000000000 1906729 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": 1418210, "vin": [ { "gen": { "height": 1418200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96574efdf99c850d835a1a953a3d589dc3f0e917c7ca728055c72f2ae6ccf81f" } } ], "extra": [ 1, 15, 31, 221, 84, 149, 183, 210, 231, 161, 142, 32, 242, 72, 62, 94, 55, 225, 80, 89, 70, 68, 254, 231, 216, 163, 133, 80, 58, 60, 6, 117, 20, 2, 17, 0, 0, 0, 6, 140, 235, 127, 9, 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