← previous blocknext block →recent activity
Analyzing
Block #87,750,407
23 transactions · 17 stateful · 2026-07-14 18:06:30 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,750,407 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w17w08w111w013w014w116w217w320w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x819b5176…86cf
0x34b655…2a6f
6 touches
3 conflicts
0xc948dbdc…199a
0x34b655…2a6f
6 touches
3 conflicts
0x9efebfcf…9e65
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x4e412b57…4771
0x34b655…2a6f
4 touches
1 conflict
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0x7c93b38a…9e69
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 0x819b5176e8…3486cf
Audit this contract →
← previous block·next block →recent activity