← previous blocknext block →recent activity
Analyzing
Block #87,512,764
25 transactions · 23 stateful · 2026-07-13 15:36:20 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,512,764 · 25 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
2w03w14w05w17w08w29w311w012w413w115w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x75ef69cd…321f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xe20a9313…c20a
0x34b655…2a6f
6 touches
3 conflicts
0xf95fb362…539f
0x34b655…2a6f
6 touches
3 conflicts
0x889bf3f8…5834
0x34b655…2a6f
6 touches
3 conflicts
0x800abf96…b7ad
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity