← previous blocknext block →recent activity
Analyzing
Block #87,291,763
11 transactions · 11 stateful · 2026-07-12 14:58:22 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,291,763 · 11 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
3w04w15w26w37w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xdbd174e4…b6f8
0x34b655…2a6f
6 touches
3 conflicts
0x2b7950c1…2342
0x34b655…2a6f
6 touches
3 conflicts
0x2e4e7336…e906
0x34b655…2a6f
6 touches
3 conflicts
0xb392c2f4…0a60
0x34b655…2a6f
6 touches
3 conflicts
0xc8024fac…da0a
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 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity