← previous blocknext block →recent activity
Analyzing
Block #87,691,311
21 transactions · 19 stateful · 2026-07-14 11:30:47 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,691,311 · 21 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
1w02w13w24w35w09w111w013w314w215w116w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b80417b…75c3
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x80d5db9f…a3fd
0x34b655…2a6f
4 touches
1 conflict
0x88ad4557…bd8d
0x34b655…2a6f
4 touches
1 conflict
0x8cc1393f…07fb
0x34b655…2a6f
4 touches
1 conflict
0x9cf61590…ad8c
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
6 conflicts on slot 0x4b80417b65…f875c3
Audit this contract →
← previous block·next block →recent activity