Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0faf3a5fb2cb17dbf2b9429db4812a8ec833c1f94e7326d9a75985f10dae203

Tx prefix hash: 72dac2a5237c8bd1256595201fef93d52686bf4cf1b693a85bad135851034c6e
Tx public key: 366e77bc7e4c1d629b376c43f876692f287d96ceb0269f71635f9728d4322b89
Timestamp: 1751628796 Timestamp [UCT]: 2025-07-04 11:33:16 Age [y:d:h:m:s]: 00:208:07:51:13
Block: 1318560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147112 RingCT/type: yes/0
Extra: 01366e77bc7e4c1d629b376c43f876692f287d96ceb0269f71635f9728d4322b89021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90f75c590f01fe514fb5a262deecd4e41ae6524bf74c0d961e94ce826e54dab7 0.600000000000 1806245 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": 1318570, "vin": [ { "gen": { "height": 1318560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90f75c590f01fe514fb5a262deecd4e41ae6524bf74c0d961e94ce826e54dab7" } } ], "extra": [ 1, 54, 110, 119, 188, 126, 76, 29, 98, 155, 55, 108, 67, 248, 118, 105, 47, 40, 125, 150, 206, 176, 38, 159, 113, 99, 95, 151, 40, 212, 50, 43, 137, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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