← previous blocknext block →recent activity
Analyzing
Block #86,928,283
16 transactions · 14 stateful · 2026-07-10 22:28:26 UTC
Parallelism
75/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,928,283 · 16 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
3w04w06w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb76f7c01…c3a5
0x34b655…2a6f
4 touches
1 conflict
0xc7f724c9…7ace
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
0x34b655…2a6f
4 touches
1 conflict
0x7babfe9a…ff96
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x09c72fc0…642a
0x34b655…2a6f
2 touches
0 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xb76f7c01e5…00c3a5
Audit this contract →
← previous block·next block →recent activity