← previous blocknext block →recent activity
Analyzing
Block #86,613,968
33 transactions · 30 stateful · 2026-07-09 11:27:03 UTC
Parallelism
67/100
Blocked
67%
Avg conflicts / tx
1.61
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,613,968 · 33 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w17w19w211w012w113w214w315w416w517w618w720w222w323w724w325w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xf7e59d30…11dd
0x34b655…2a6f
8 touches
6 conflicts
0x12573732…e891
0x34b655…2a6f
8 touches
6 conflicts
0x60c7217a…8c94
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity