← previous blocknext block →recent activity
Analyzing
Block #86,233,266
24 transactions · 18 stateful · 2026-07-07 17:01:48 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,233,266 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w210w012w013w116w017w121w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x513d7ed9…f0ae
0xd32edf…ff58
5 touches
3 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0x921b0818…fd01
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x41233cb1…abeb
0x188d58…ea8e
2 touches
0 conflicts
0x41233cb1…abec
0x188d58…ea8e
2 touches
0 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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity