← previous blocknext block →recent activity
Analyzing
Block #87,751,439
20 transactions · 16 stateful · 2026-07-14 18:13:24 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,751,439 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w09w113w014w215w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f461725…5ab2
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x77aa49e7…df90
0x34b655…2a6f
6 touches
3 conflicts
0x6f46250b…3bf2
0x34b655…2a6f
6 touches
3 conflicts
0x3a529fe7…de9a
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x4c214bb3…c5d3
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 0x2f4617255d…ea5ab2
Audit this contract →
← previous block·next block →recent activity