← previous blocknext block →recent activity
Analyzing
Block #87,902,943
18 transactions · 18 stateful · 2026-07-15 11:06:48 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,902,943 · 18 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
5w06w07w19w110w211w313w416w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x9f83113a…dcd8
0x34b655…2a6f
8 touches
6 conflicts
0xf092652d…787f
0x34b655…2a6f
6 touches
3 conflicts
0x8f2d72a5…5d65
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x9af03de8…05b0
0x34b655…2a6f
6 touches
3 conflicts
0xa90aa7ad…403b
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity