← previous blocknext block →recent activity
Analyzing
Block #87,920,924
14 transactions · 13 stateful · 2026-07-15 13:07:03 UTC
Parallelism
57/100
Blocked
46%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,920,924 · 14 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
1w03w15w26w37w48w513w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x27c2d73e…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc788862c…c259
0x34b655…2a6f
8 touches
6 conflicts
0x6689d73a…ba50
0x34b655…2a6f
6 touches
3 conflicts
0x4c623175…29e4
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7d6e48e8…f2b5
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity