← previous blocknext block →recent activity
Analyzing
Block #86,990,003
9 transactions · 8 stateful · 2026-07-11 05:20:49 UTC
Parallelism
44/100
Blocked
63%
Avg conflicts / tx
1.22
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,990,003 · 9 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
2w03w14w25w36w17w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x814f0f40…c654
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x619c81de…01b4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd7320039…3bbf
0x34b655…2a6f
6 touches
3 conflicts
0xd7320039…3bc0
0x34b655…2a6f
6 touches
3 conflicts
0xdd38f4e6…586c
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 0x814f0f40f3…5dc654
Audit this contract →
← previous block·next block →recent activity