← previous blocknext block →recent activity
Analyzing
Block #87,064,209
20 transactions · 18 stateful · 2026-07-11 13:36:36 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,064,209 · 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
1w03w14w16w07w210w112w114w215w217w319w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56856c67…fe45
0x34b655…2a6f
6 touches
3 conflicts
0xf6f85101…0407
0x34b655…2a6f
6 touches
3 conflicts
0xda65cebb…3038
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
6 touches
3 conflicts
0x426767f7…4561
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a3
0x34b655…2a6f
6 touches
3 conflicts
0x798d2045…4975
0x34b655…2a6f
6 touches
3 conflicts
0xf5fbbfcd…3c8d
0xd32edf…ff58
5 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
3 conflicts on slot 0x56856c6721…62fe45
Audit this contract →
← previous block·next block →recent activity