← previous blocknext block →recent activity
Analyzing
Block #87,919,083
22 transactions · 19 stateful · 2026-07-15 12:54:43 UTC
Parallelism
77/100
Blocked
37%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,919,083 · 22 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
5w06w111w112w213w314w416w319w020w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebeee24a…ed8d
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x501c6ac7…768e
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x2e64e234…5cfa
0x34b655…2a6f
4 touches
1 conflict
0x2e92eb56…31c2
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 0xebeee24aff…40ed8d
Audit this contract →
← previous block·next block →recent activity