Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6c12acbdd6fe046a81c9d16edd2226dbb4a3d86684fc4c3913ba0e3cfe4f9ce

Tx prefix hash: e54a9134c316303593331a96ef2a0abc878980fef6a2de28a1ac19c38a871698
Tx public key: 4ed57c29c5a564c961496c979a3c1ed16b1825122b9756d83d4cf5aee9b12e97
Timestamp: 1746902609 Timestamp [UCT]: 2025-05-10 18:43:29 Age [y:d:h:m:s]: 00:194:07:01:44
Block: 1280056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136565 RingCT/type: yes/0
Extra: 014ed57c29c5a564c961496c979a3c1ed16b1825122b9756d83d4cf5aee9b12e970211000000049f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c995e5b6ea9a6ee1bd166c332355a9f666b7f8249d20b73d7d5fc4867336bb7e 0.600000000000 1767439 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": 1280066, "vin": [ { "gen": { "height": 1280056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c995e5b6ea9a6ee1bd166c332355a9f666b7f8249d20b73d7d5fc4867336bb7e" } } ], "extra": [ 1, 78, 213, 124, 41, 197, 165, 100, 201, 97, 73, 108, 151, 154, 60, 30, 209, 107, 24, 37, 18, 43, 151, 86, 216, 61, 76, 245, 174, 233, 177, 46, 151, 2, 17, 0, 0, 0, 4, 159, 159, 230, 140, 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