Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 205367eacc47a95e75e4e9a7562c66007b931540726840aaa029131724e383f9

Tx prefix hash: 87059c96354530f9ee14fd0fbdbd7d9ff20cc793435ba5f0560b550b3cfca780
Tx public key: 1d739209c58257c5fe167c3f2d977afa5d8d809da2cb561ccf820959aa0ec5bd
Timestamp: 1735126509 Timestamp [UCT]: 2024-12-25 11:35:09 Age [y:d:h:m:s]: 00:098:21:28:29
Block: 1182847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70454 RingCT/type: yes/0
Extra: 011d739209c58257c5fe167c3f2d977afa5d8d809da2cb561ccf820959aa0ec5bd0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a90d3c69fd427e9e995a74159075d920dfe682e959506c20c2d26208e84e5c8 0.600000000000 1669286 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": 1182857, "vin": [ { "gen": { "height": 1182847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a90d3c69fd427e9e995a74159075d920dfe682e959506c20c2d26208e84e5c8" } } ], "extra": [ 1, 29, 115, 146, 9, 197, 130, 87, 197, 254, 22, 124, 63, 45, 151, 122, 250, 93, 141, 128, 157, 162, 203, 86, 28, 207, 130, 9, 89, 170, 14, 197, 189, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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