← previous blocknext block →recent activity
Analyzing
Block #86,626,067
32 transactions · 26 stateful · 2026-07-09 12:47:49 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,626,067 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w013w018w119w226w127w228w329w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x39572420…1d7c
0x34b655…2a6f
6 touches
3 conflicts
0x2bcdd4a1…3d3a
0x34b655…2a6f
6 touches
3 conflicts
0xa1c2f944…c829
0xd32edf…ff58
5 touches
3 conflicts
0xa29182a1…c12c
0x34b655…2a6f
4 touches
1 conflict
0x0a9a1df9…6b66
0x34b655…2a6f
4 touches
1 conflict
0xe6805ef8…e22e
0x34b655…2a6f
4 touches
1 conflict
0xf8f1e808…a4fd
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity