← previous blocknext block →recent activity
Analyzing
Block #86,811,936
9 transactions · 8 stateful · 2026-07-10 09:30:26 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,811,936 · 9 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
1w04w15w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d888c90…5479
0x34b655…2a6f
8 touches
6 conflicts
0x30643e3a…dc6f
0x34b655…2a6f
4 touches
1 conflict
0xb7b8bfda…efc0
0x34b655…2a6f
4 touches
1 conflict
0x0a5a4598…01bc
0x34b655…2a6f
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x3eede796…d745
0x34b655…2a6f
2 touches
0 conflicts
0x58f65aa1…8f98
0x34b655…2a6f
2 touches
0 conflicts
0x5f02e0ec…15da
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
6 conflicts on slot 0x8d888c9003…aa5479
Audit this contract →
← previous block·next block →recent activity