← previous blocknext block →recent activity
Analyzing
Block #87,918,350
17 transactions · 16 stateful · 2026-07-15 12:49:49 UTC
Parallelism
53/100
Blocked
44%
Avg conflicts / tx
0.88
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,918,350 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w411w512w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x2000b734…5e5a
0x34b655…2a6f
4 touches
1 conflict
0x2b2cf495…1c6f
0x34b655…2a6f
4 touches
1 conflict
0x2ccd8c61…48f2
0x34b655…2a6f
4 touches
1 conflict
0x3559c176…9fe1
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