← previous blocknext block →recent activity
Analyzing
Block #86,989,418
20 transactions · 20 stateful · 2026-07-11 05:16:55 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,989,418 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w16w07w111w012w113w215w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c7e1952…d9c9
0x34b655…2a6f
8 touches
6 conflicts
0x7d6e48e8…f2b5
0x34b655…2a6f
6 touches
3 conflicts
0xd33a109e…bdb6
0x34b655…2a6f
6 touches
3 conflicts
0xdd38f4e6…586c
0x34b655…2a6f
6 touches
3 conflicts
0x619c81de…01b4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x6c7e195218…27d9c9
Audit this contract →
← previous block·next block →recent activity