Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c35c1a06b30713e5a826976d71fa9492b0944609d793efeec7cfb95fc59dd553

Tx prefix hash: 0293d10eb976f32936601bce827b00a553af1e77dc3eb669e2194933eaafa9b0
Tx public key: f112f4d5500c941a9fdaf9b8947f7107d95a5a7fe8889c2a8170ef9691a20cc7
Timestamp: 1766281368 Timestamp [UCT]: 2025-12-21 01:42:48 Age [y:d:h:m:s]: 00:019:15:50:42
Block: 1438124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14069 RingCT/type: yes/0
Extra: 01f112f4d5500c941a9fdaf9b8947f7107d95a5a7fe8889c2a8170ef9691a20cc70211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c21c8ec83ed757ad977ae9e5f9644ea982abe092d514f4c97c317419d993bf9c 0.600000000000 1926941 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": 1438134, "vin": [ { "gen": { "height": 1438124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c21c8ec83ed757ad977ae9e5f9644ea982abe092d514f4c97c317419d993bf9c" } } ], "extra": [ 1, 241, 18, 244, 213, 80, 12, 148, 26, 159, 218, 249, 184, 148, 127, 113, 7, 217, 90, 90, 127, 232, 136, 156, 42, 129, 112, 239, 150, 145, 162, 12, 199, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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