Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf188d61284d6f80c02eb58623d0a87e8899f673e3e9fd5eef2a1ba1f2810d5f

Tx prefix hash: c0348109bf922fc868115753ccfb76e81f94df44cdc94890f2ba72cc1c329560
Tx public key: f2b80de88f8319513ffbc0eab3b70c5468c2f6c30a8b6ef879c5a472ada46512
Timestamp: 1749393064 Timestamp [UCT]: 2025-06-08 14:31:04 Age [y:d:h:m:s]: 00:159:10:06:09
Block: 1300694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111613 RingCT/type: yes/0
Extra: 01f2b80de88f8319513ffbc0eab3b70c5468c2f6c30a8b6ef879c5a472ada46512021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0904298c2db07c04264e2156cecc1be977e8d31954c781bdd6cf9c38c65f2e56 0.600000000000 1788243 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": 1300704, "vin": [ { "gen": { "height": 1300694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0904298c2db07c04264e2156cecc1be977e8d31954c781bdd6cf9c38c65f2e56" } } ], "extra": [ 1, 242, 184, 13, 232, 143, 131, 25, 81, 63, 251, 192, 234, 179, 183, 12, 84, 104, 194, 246, 195, 10, 139, 110, 248, 121, 197, 164, 114, 173, 164, 101, 18, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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