← previous blocknext block →recent activity
Analyzing
Block #87,902,381
19 transactions · 18 stateful · 2026-07-15 11:03:02 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,902,381 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w19w210w313w414w517w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xebe9512d…5162
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x9f287382…28e5
0x34b655…2a6f
6 touches
3 conflicts
0xf2e22c06…42d6
0x34b655…2a6f
6 touches
3 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
4 touches
1 conflict
0x3b0c8e76…5929
0x34b655…2a6f
4 touches
1 conflict
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity