Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1b7a263f970efdde4e463d597c80fe443f1cb9186291eb89aaf840d5a19beb9

Tx prefix hash: 643cb8f995c9cb561577b7fff601e0b2bd58ab4ef75e8a468593454e5c24f3a6
Tx public key: 12cf6f99f0de515719b3599c7108eb05fb62e6b06ea9b534774183c6f6a96b40
Timestamp: 1721343907 Timestamp [UCT]: 2024-07-18 23:05:07 Age [y:d:h:m:s]: 00:297:21:14:16
Block: 1068710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212826 RingCT/type: yes/0
Extra: 0112cf6f99f0de515719b3599c7108eb05fb62e6b06ea9b534774183c6f6a96b40021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f525f036035a9220629bed1394048c65712f5440816662817d5d645e21e596a 0.600000000000 1539847 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": 1068720, "vin": [ { "gen": { "height": 1068710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f525f036035a9220629bed1394048c65712f5440816662817d5d645e21e596a" } } ], "extra": [ 1, 18, 207, 111, 153, 240, 222, 81, 87, 25, 179, 89, 156, 113, 8, 235, 5, 251, 98, 230, 176, 110, 169, 181, 52, 119, 65, 131, 198, 246, 169, 107, 64, 2, 17, 0, 0, 0, 8, 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