← previous blocknext block →recent activity
Analyzing
Block #86,810,306
21 transactions · 16 stateful · 2026-07-10 09:19:31 UTC
Parallelism
81/100
Blocked
63%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,810,306 · 21 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
1w02w15w06w17w28w39w110w212w213w314w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x202c03eb…cf33
0xa6afd3…d132
8 touches
6 conflicts
0xdec5bfea…d17f
0xa6afd3…d132
8 touches
6 conflicts
0x772ab420…c2f6
0x34b655…2a6f
6 touches
3 conflicts
0xec7fe04a…3c56
0x34b655…2a6f
6 touches
3 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0xa37e64f8…ba05
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity