Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57daf08e97924e5930fe9502f0eb2ff839e4659cbaef7da5ae877715f56c46bc

Tx prefix hash: 093ca260a9976d69289edb073da1483d1a9d4c990ab42a6a4a0badfa9422318c
Tx public key: 96eb660e6017ec080f6768e8ccf3add6c79bcf7c1364a0c01f5bf163d276ac3a
Timestamp: 1721251068 Timestamp [UCT]: 2024-07-17 21:17:48 Age [y:d:h:m:s]: 00:129:09:30:21
Block: 1067937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92578 RingCT/type: yes/0
Extra: 0196eb660e6017ec080f6768e8ccf3add6c79bcf7c1364a0c01f5bf163d276ac3a02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68e3872bb336fa29f479b171c2c310fdc7cd28bcc540a0050d4cfeec14d2e747 0.600000000000 1538886 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": 1067947, "vin": [ { "gen": { "height": 1067937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68e3872bb336fa29f479b171c2c310fdc7cd28bcc540a0050d4cfeec14d2e747" } } ], "extra": [ 1, 150, 235, 102, 14, 96, 23, 236, 8, 15, 103, 104, 232, 204, 243, 173, 214, 199, 155, 207, 124, 19, 100, 160, 192, 31, 91, 241, 99, 210, 118, 172, 58, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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