← previous blocknext block →recent activity
Analyzing
Block #87,920,380
23 transactions · 21 stateful · 2026-07-15 13:03:24 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,920,380 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w110w211w312w413w520w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79ace5b6…8d37
0x34b655…2a6f
8 touches
6 conflicts
0x95dc7164…65e5
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x93b25946…9160
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 0x79ace5b6d1…c68d37
Audit this contract →
← previous block·next block →recent activity