Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 566d74f417bcf1ee374acc3dba4a90bd8024b89dc1644b9b94aa17b9fb7c836a

Tx prefix hash: 1d5bc14c00fe144a23fcf969ab109678e053b8fc41962aa6d9acbf033039d4f4
Tx public key: ad24eba851a40448d3fb46ec9ef9fb25909a2ad800ab61d3945f32ddfdaa87dd
Timestamp: 1763019741 Timestamp [UCT]: 2025-11-13 07:42:21 Age [y:d:h:m:s]: 00:076:11:57:24
Block: 1411083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54597 RingCT/type: yes/0
Extra: 01ad24eba851a40448d3fb46ec9ef9fb25909a2ad800ab61d3945f32ddfdaa87dd02110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d416c81dee91ac2636a2e699b0406b7df84e9ec6fe031cedea95d45b715e3e4e 0.600000000000 1899540 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": 1411093, "vin": [ { "gen": { "height": 1411083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d416c81dee91ac2636a2e699b0406b7df84e9ec6fe031cedea95d45b715e3e4e" } } ], "extra": [ 1, 173, 36, 235, 168, 81, 164, 4, 72, 211, 251, 70, 236, 158, 249, 251, 37, 144, 154, 42, 216, 0, 171, 97, 211, 148, 95, 50, 221, 253, 170, 135, 221, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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