Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df5ff0c2c7fb674e0db88e9972a4f24326b4f57f2867ac72f09f21d9c63cd42b

Tx prefix hash: b160cdf7e8d227a5afc860c13c103ee5f68a10323b2e34870f1a3fcd28745323
Tx public key: 111e057dbdf35f0b5e5e8a2d0618c8cac1dee521e6766eaae4fce16debb2a19a
Timestamp: 1735272466 Timestamp [UCT]: 2024-12-27 04:07:46 Age [y:d:h:m:s]: 00:090:22:38:49
Block: 1184045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64782 RingCT/type: yes/0
Extra: 01111e057dbdf35f0b5e5e8a2d0618c8cac1dee521e6766eaae4fce16debb2a19a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8245ab1f9024082febdd31fec673bf37cc2e70e0ed3d81367d92011b5c28e812 0.600000000000 1670498 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": 1184055, "vin": [ { "gen": { "height": 1184045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8245ab1f9024082febdd31fec673bf37cc2e70e0ed3d81367d92011b5c28e812" } } ], "extra": [ 1, 17, 30, 5, 125, 189, 243, 95, 11, 94, 94, 138, 45, 6, 24, 200, 202, 193, 222, 229, 33, 230, 118, 110, 170, 228, 252, 225, 109, 235, 178, 161, 154, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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