← previous blocknext block →recent activity
Analyzing
Block #87,584,191
27 transactions · 19 stateful · 2026-07-13 23:34:46 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,584,191 · 27 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
1w03w14w05w16w210w011w112w213w317w419w226w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
10 touches
10 conflicts
0xd201f2b2…8a43
0x34b655…2a6f
8 touches
6 conflicts
0x97a4d3d6…7096
0x34b655…2a6f
8 touches
6 conflicts
0x983e6564…18eb
0x34b655…2a6f
8 touches
6 conflicts
0xd0243b19…507b
0x34b655…2a6f
8 touches
6 conflicts
0x992fec28…420d
0x34b655…2a6f
8 touches
6 conflicts
0x75f928fc…0465
0x34b655…2a6f
8 touches
6 conflicts
0x6c87ba93…686c
0x34b655…2a6f
8 touches
6 conflicts
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
10 conflicts on slot 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity