← previous blocknext block →recent activity
Analyzing
Block #86,733,281
16 transactions · 14 stateful · 2026-07-10 00:45:03 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,733,281 · 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
2w04w05w16w28w09w110w111w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xa42e8482…b88f
0x34b655…2a6f
8 touches
6 conflicts
0x0d4e5638…fb77
0x34b655…2a6f
6 touches
3 conflicts
0x12dca7b0…a0dd
0x34b655…2a6f
6 touches
3 conflicts
0x1e7927e5…282d
0x34b655…2a6f
6 touches
3 conflicts
0x405861f3…97d0
0x34b655…2a6f
6 touches
3 conflicts
0x642214b2…c084
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity