Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f258ffac1e8f82e93272532333cf71395dc5a71d43232fba4da3137906bb9385

Tx prefix hash: 3635267fa425f65cb366057bbda479f452b4d4680712a367d7b924dee8d1ebda
Tx public key: 5d5882c7e2e75591fb5a20914cc4844ec76d7d6c8379223bf58416b2e6b95b1f
Timestamp: 1725585050 Timestamp [UCT]: 2024-09-06 01:10:50 Age [y:d:h:m:s]: 00:208:16:12:42
Block: 1103861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148976 RingCT/type: yes/0
Extra: 015d5882c7e2e75591fb5a20914cc4844ec76d7d6c8379223bf58416b2e6b95b1f021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 104759bc704eff19b6e40ec004997d31582148f9f57e0aa25e5c37d88b6fc9de 0.600000000000 1580850 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": 1103871, "vin": [ { "gen": { "height": 1103861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "104759bc704eff19b6e40ec004997d31582148f9f57e0aa25e5c37d88b6fc9de" } } ], "extra": [ 1, 93, 88, 130, 199, 226, 231, 85, 145, 251, 90, 32, 145, 76, 196, 132, 78, 199, 109, 125, 108, 131, 121, 34, 59, 245, 132, 22, 178, 230, 185, 91, 31, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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