Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9985317d3952f14ff5c48f3a3a98a578993a0fd4a2457dd15238ab666316da40

Tx prefix hash: ef441f513e1dce6fff6036a3df204e953b4ef40b96475081458ceec8b34f4bf0
Tx public key: 6a1e8d1acdd6b145b54d9d125ba1921c14e0874bf7694f242571063e3f0e5386
Timestamp: 1720209290 Timestamp [UCT]: 2024-07-05 19:54:50 Age [y:d:h:m:s]: 00:319:01:35:02
Block: 1059280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228027 RingCT/type: yes/0
Extra: 016a1e8d1acdd6b145b54d9d125ba1921c14e0874bf7694f242571063e3f0e538602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ec4527052157b05cdcee0daf97c7421154b94b2cbece97306f71114a7a5797c 0.600000000000 1529747 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": 1059290, "vin": [ { "gen": { "height": 1059280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ec4527052157b05cdcee0daf97c7421154b94b2cbece97306f71114a7a5797c" } } ], "extra": [ 1, 106, 30, 141, 26, 205, 214, 177, 69, 181, 77, 157, 18, 91, 161, 146, 28, 20, 224, 135, 75, 247, 105, 79, 36, 37, 113, 6, 62, 63, 14, 83, 134, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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