Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cd413670c19ab55c1ecba106a8a81cec3d24eb40e3c782c51b4cedd3e35a5b3

Tx prefix hash: b422d990c142e5c2a7742e4ac1516eabd4272ba47ec0e3352dcda78b85be98ca
Tx public key: da444749a65a9d3e640706e83829165ec44b78dcd6ce4eb9b4ecb218a36ec9d3
Timestamp: 1745494825 Timestamp [UCT]: 2025-04-24 11:40:25 Age [y:d:h:m:s]: 00:276:08:08:12
Block: 1268411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195124 RingCT/type: yes/0
Extra: 01da444749a65a9d3e640706e83829165ec44b78dcd6ce4eb9b4ecb218a36ec9d30211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 052a07c1e9b4a92c19cc687cf5e1be0566196b6f64ff2f5ac6ff65e24f61e426 0.600000000000 1755640 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": 1268421, "vin": [ { "gen": { "height": 1268411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "052a07c1e9b4a92c19cc687cf5e1be0566196b6f64ff2f5ac6ff65e24f61e426" } } ], "extra": [ 1, 218, 68, 71, 73, 166, 90, 157, 62, 100, 7, 6, 232, 56, 41, 22, 94, 196, 75, 120, 220, 214, 206, 78, 185, 180, 236, 178, 24, 163, 110, 201, 211, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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