Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68d64da55e2d7dfcf72980763f9e3cecc823ba6ede6bab82d094eb2555e039b0

Tx prefix hash: 19722eb1298c3ac223f0d8cc7e2d4df5063aa9b6dacfa130b1cd6768207e085a
Tx public key: 86cc9369e8c7d95e28520ebfb20cf21475bc3f3dd0aca831abc783bfc9de1981
Timestamp: 1667416115 Timestamp [UCT]: 2022-11-02 19:08:35 Age [y:d:h:m:s]: 02:363:03:17:48
Block: 622597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 778914 RingCT/type: yes/0
Extra: 0186cc9369e8c7d95e28520ebfb20cf21475bc3f3dd0aca831abc783bfc9de19810211000000028b7b6602000000000000000000

1 output(s) for total of 5.309794501000 dcy

stealth address amount amount idx
00: 26260b7b716e55d7c83e86b2e98a63c9ac9bb84f8ee08fd24be7ab95ca9752f6 5.309794501000 1060684 of 0

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": 622607, "vin": [ { "gen": { "height": 622597 } } ], "vout": [ { "amount": 5309794501, "target": { "key": "26260b7b716e55d7c83e86b2e98a63c9ac9bb84f8ee08fd24be7ab95ca9752f6" } } ], "extra": [ 1, 134, 204, 147, 105, 232, 199, 217, 94, 40, 82, 14, 191, 178, 12, 242, 20, 117, 188, 63, 61, 208, 172, 168, 49, 171, 199, 131, 191, 201, 222, 25, 129, 2, 17, 0, 0, 0, 2, 139, 123, 102, 2, 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