Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 092fa7f52ddf4b3e8cb9cdb6d6c79563a87cad86555f0634f6f09af2d9585078

Tx prefix hash: 0e722f043b719cc09a1e5f702a5149324ccf3a4dcf1a68684487b0950c059ea4
Tx public key: 4297189ac11295a2b98ec70f3e4859e4b205a592c670a2e6ae91b95fcf26216f
Timestamp: 1756690156 Timestamp [UCT]: 2025-09-01 01:29:16 Age [y:d:h:m:s]: 00:129:15:50:56
Block: 1358754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92721 RingCT/type: yes/0
Extra: 014297189ac11295a2b98ec70f3e4859e4b205a592c670a2e6ae91b95fcf26216f021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c48f1ebbbdf36f749175a78f1b8f9651bf2fc348363df83d4e97729d32f1bb2a 0.600000000000 1846767 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": 1358764, "vin": [ { "gen": { "height": 1358754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c48f1ebbbdf36f749175a78f1b8f9651bf2fc348363df83d4e97729d32f1bb2a" } } ], "extra": [ 1, 66, 151, 24, 154, 193, 18, 149, 162, 185, 142, 199, 15, 62, 72, 89, 228, 178, 5, 165, 146, 198, 112, 162, 230, 174, 145, 185, 95, 207, 38, 33, 111, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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