← previous blocknext block →recent activity
Analyzing
Block #87,918,282
22 transactions · 20 stateful · 2026-07-15 12:49:22 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.45
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,918,282 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w09w110w211w313w314w415w516w620w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf58b2d27…e4eb
0x34b655…2a6f
8 touches
6 conflicts
0xaf34ae1c…04db
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x76c4467d…ce28
0x34b655…2a6f
6 touches
3 conflicts
0x3800d0ea…6168
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
15 conflicts on slot 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity