Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0cdf766eed601e07ead35d2ddc6aa2a4e2af2817bf899eb7e92bf6521d9c16e

Tx prefix hash: 87d19c6588ca786407ac066f74f3fa06a500dfc936a4dc04d0a1255e9f47492e
Tx public key: cad4bd65548f0190cfe95b02dfd4bd39b32cb11ea30c922f096b50700b4c6b43
Timestamp: 1766260323 Timestamp [UCT]: 2025-12-20 19:52:03 Age [y:d:h:m:s]: 00:000:18:41:11
Block: 1437939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554 RingCT/type: yes/0
Extra: 01cad4bd65548f0190cfe95b02dfd4bd39b32cb11ea30c922f096b50700b4c6b43021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b004bfb79d6c8405ebd82c88f25137d107fe9e5443011c753e5b24ec5d375423 0.600000000000 1926752 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": 1437949, "vin": [ { "gen": { "height": 1437939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b004bfb79d6c8405ebd82c88f25137d107fe9e5443011c753e5b24ec5d375423" } } ], "extra": [ 1, 202, 212, 189, 101, 84, 143, 1, 144, 207, 233, 91, 2, 223, 212, 189, 57, 179, 44, 177, 30, 163, 12, 146, 47, 9, 107, 80, 112, 11, 76, 107, 67, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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