Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 165fb77f5b3d820100f312c0f70232c0533883a3ab333e4471ea9e8c7b7193f5

Tx prefix hash: 6988660f2e272c723b93c969f5677b711f53f0729eaf89b3e4102fa6f7dc6cbd
Tx public key: c6de35c322e0e2b949c90af5cd487c4a9f932859b470c6a7e0bfcbc530d2c0b9
Timestamp: 1708761073 Timestamp [UCT]: 2024-02-24 07:51:13 Age [y:d:h:m:s]: 01:030:19:00:16
Block: 964382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283005 RingCT/type: yes/0
Extra: 01c6de35c322e0e2b949c90af5cd487c4a9f932859b470c6a7e0bfcbc530d2c0b902110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccdb07892ed74dd33de3d27b647cf7041afce24f0d4db4f64e9fbe03aa3c1213 0.600000000000 1424113 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": 964392, "vin": [ { "gen": { "height": 964382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccdb07892ed74dd33de3d27b647cf7041afce24f0d4db4f64e9fbe03aa3c1213" } } ], "extra": [ 1, 198, 222, 53, 195, 34, 224, 226, 185, 73, 201, 10, 245, 205, 72, 124, 74, 159, 147, 40, 89, 180, 112, 198, 167, 224, 191, 203, 197, 48, 210, 192, 185, 2, 17, 0, 0, 0, 6, 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