← previous blocknext block →recent activity
Analyzing
Block #86,627,457
36 transactions · 29 stateful · 2026-07-09 12:57:05 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
0.72
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,627,457 · 36 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w18w09w111w012w113w214w315w018w020w121w222w426w227w330w132w533w634w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
8 touches
6 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x342fbbca…d443
0x40c49f…2af0
6 touches
3 conflicts
0xea02471d…1542
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity