← previous blocknext block →recent activity
Analyzing
Block #87,661,413
23 transactions · 18 stateful · 2026-07-14 08:10:59 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,661,413 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05b1b07a…7a99
0x34b655…2a6f
16 touches
28 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x75b43fdd…8dc1
0x34b655…2a6f
16 touches
28 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
16 touches
28 conflicts
0x9fd37234…2731
0x34b655…2a6f
16 touches
28 conflicts
0xd7fd3b1f…f930
0x34b655…2a6f
16 touches
28 conflicts
0xf3e18c38…f1b9
0x34b655…2a6f
16 touches
28 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
28 conflicts on slot 0x05b1b07aba…747a99
Audit this contract →
← previous block·next block →recent activity