← previous blocknext block →recent activity
Analyzing
Block #85,509,263
30 transactions · 26 stateful · 2026-07-04 08:34:03 UTC
Parallelism
77/100
Blocked
65%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,509,263 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w110w211w312w415w018w119w220w521w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x9ff176a9…152e
0x065c9d…c394
8 touches
6 conflicts
0x9a555477…19a8
0x754704…b603
8 touches
6 conflicts
0x00000000…0004
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…0002
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…0000
0x63e48b…53f2
8 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity