← previous blocknext block →recent activity
Analyzing
Block #87,705,595
33 transactions · 25 stateful · 2026-07-14 13:06:33 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,705,595 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w09w110w212w113w219w321w022w127w128w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x367b69ad…33d9
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x367b69ad…33d8
0x34b655…2a6f
6 touches
3 conflicts
0xfa786afc…9dd2
0x34b655…2a6f
6 touches
3 conflicts
0x5ec64628…72e4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x367b69ad60…4333d9
Audit this contract →
← previous block·next block →recent activity