← previous blocknext block →recent activity
Analyzing
Block #86,914,007
30 transactions · 23 stateful · 2026-07-10 20:53:02 UTC
Parallelism
70/100
Blocked
57%
Avg conflicts / tx
1.3
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,914,007 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w08w113w014w115w216w317w418w519w623w626w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xb06917e8…6985
0x34b655…2a6f
12 touches
15 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
10 touches
10 conflicts
0x071e17d4…fd91
0x34b655…2a6f
10 touches
10 conflicts
0x5a19ef35…dc70
0x34b655…2a6f
10 touches
10 conflicts
0xaf498679…7732
0x34b655…2a6f
10 touches
10 conflicts
0xbc7b467b…1fef
0x34b655…2a6f
10 touches
10 conflicts
0xa9cbb623…e644
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity