← previous blocknext block →recent activity
Analyzing
Block #86,926,369
25 transactions · 23 stateful · 2026-07-10 22:15:41 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,926,369 · 25 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
1w02w13w06w212w014w115w216w317w318w120w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x988c5bc8…ce1b
0x065c9d…c394
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xa248a5dd…4a69
0x34b655…2a6f
6 touches
3 conflicts
0x324ac977…a8dd
0x34b655…2a6f
6 touches
3 conflicts
0xc3412055…65dd
0x34b655…2a6f
6 touches
3 conflicts
0xc3412055…65de
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity