← previous blocknext block →recent activity
Analyzing
Block #87,753,102
18 transactions · 14 stateful · 2026-07-14 18:24:31 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,753,102 · 18 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
3w05w16w27w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34bcdc05…6689
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x199944d5…ab9f
0x34b655…2a6f
6 touches
3 conflicts
0x367b69ad…33d9
0x34b655…2a6f
4 touches
1 conflict
0x3a1edb3e…b841
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
15 conflicts on slot 0x34bcdc05ee…2c6689
Audit this contract →
← previous block·next block →recent activity