← previous blocknext block →recent activity
Analyzing
Block #87,615,793
12 transactions · 11 stateful · 2026-07-14 03:06:06 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,615,793 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w17w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbdd60dd…f294
0x34b655…2a6f
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0x295faadc…ed75
0x34b655…2a6f
4 touches
1 conflict
0x0198fc89…5f6d
0x34b655…2a6f
4 touches
1 conflict
0x3cb8c8c3…22f4
0x34b655…2a6f
4 touches
1 conflict
0x3f25409b…f92b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5f251b96…6054
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
1 conflict on slot 0xdbdd60dde3…b6f294
Audit this contract →
← previous block·next block →recent activity