← previous blocknext block →recent activity
Analyzing
Block #87,354,743
11 transactions · 9 stateful · 2026-07-12 21:59:26 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,354,743 · 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
4w05w16w28w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x1f5dc61b…2471
0x34b655…2a6f
6 touches
3 conflicts
0xa1185d34…5818
0x34b655…2a6f
4 touches
1 conflict
0x94ab81a0…5e6b
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity