← previous blocknext block →recent activity
Analyzing
Block #87,302,909
17 transactions · 13 stateful · 2026-07-12 16:12:50 UTC
Parallelism
76/100
Blocked
46%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,302,909 · 17 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
1w02w13w28w09w110w215w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f461725…5ab2
0x34b655…2a6f
6 touches
3 conflicts
0xeef314d6…5394
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xac3e4969…39e9
0x34b655…2a6f
6 touches
3 conflicts
0x875c3459…2878
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe93787bf…3f09
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 0x2f4617255d…ea5ab2
Audit this contract →
← previous block·next block →recent activity