Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccdf691f966b6128b03904d874738f9e1338562c238a636c5f8d3366870b7878

Tx prefix hash: b08602180e6b0c26ecdc5bf3e4c4b014ef43385608fa541129c2b87812535847
Tx public key: 6786b93c0d41b245e3161ba43e89ab84fdfa948c5130dcaf807f696436db0cd6
Timestamp: 1732883697 Timestamp [UCT]: 2024-11-29 12:34:57 Age [y:d:h:m:s]: 00:354:02:04:48
Block: 1164272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250599 RingCT/type: yes/0
Extra: 016786b93c0d41b245e3161ba43e89ab84fdfa948c5130dcaf807f696436db0cd60211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc012f7fe7df40a3d5b732ac4081bb9b22b3c92e930acfb19049352f20991adb 0.600000000000 1649945 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": 1164282, "vin": [ { "gen": { "height": 1164272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc012f7fe7df40a3d5b732ac4081bb9b22b3c92e930acfb19049352f20991adb" } } ], "extra": [ 1, 103, 134, 185, 60, 13, 65, 178, 69, 227, 22, 27, 164, 62, 137, 171, 132, 253, 250, 148, 140, 81, 48, 220, 175, 128, 127, 105, 100, 54, 219, 12, 214, 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