Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 566b0a5c9ec94533ace8e6cfa2dd0705512da30c33ba2a5dd63f3e5ed94330d5

Tx prefix hash: c776bd6bab2c8446dff52796cecf662114b22597688cd31b0bbddb5ff3f68b6a
Tx public key: 8a523578b28292632fb05ce09d61475096594f632542db6ed092efd0d7ed6f3b
Timestamp: 1727399741 Timestamp [UCT]: 2024-09-27 01:15:41 Age [y:d:h:m:s]: 00:211:22:08:07
Block: 1118905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151281 RingCT/type: yes/0
Extra: 018a523578b28292632fb05ce09d61475096594f632542db6ed092efd0d7ed6f3b02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0e8fc6ea856c62f799c8e6f376482433b3c21a7748f79f971c9f43c18c50f1a 0.600000000000 1600262 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": 1118915, "vin": [ { "gen": { "height": 1118905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0e8fc6ea856c62f799c8e6f376482433b3c21a7748f79f971c9f43c18c50f1a" } } ], "extra": [ 1, 138, 82, 53, 120, 178, 130, 146, 99, 47, 176, 92, 224, 157, 97, 71, 80, 150, 89, 79, 99, 37, 66, 219, 110, 208, 146, 239, 208, 215, 237, 111, 59, 2, 17, 0, 0, 0, 10, 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