← previous blocknext block →recent activity
Analyzing
Block #87,357,921
18 transactions · 16 stateful · 2026-07-12 22:20:41 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.28
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,357,921 · 18 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
3w04w05w111w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff9c8b2d…bda7
0x34b655…2a6f
4 touches
1 conflict
0xf7ef0c17…df1d
0x34b655…2a6f
4 touches
1 conflict
0xf81d0d0f…cf78
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x4e3abeff…18eb
0x34b655…2a6f
4 touches
1 conflict
0x6762cac2…3fb0
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
0x34b655…2a6f
4 touches
1 conflict
0x6c432ccf…2728
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
1 conflict on slot 0xff9c8b2d7f…d0bda7
Audit this contract →
← previous block·next block →recent activity