← previous blocknext block →recent activity
Analyzing
Block #86,273,363
30 transactions · 27 stateful · 2026-07-07 21:29:33 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,273,363 · 30 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
1w02w13w05w16w27w310w011w114w018w121w222w425w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x04b52208…fdd6
0x34b655…2a6f
4 touches
1 conflict
0x0c366266…77e1
0x34b655…2a6f
4 touches
1 conflict
0x0eeb2a30…6909
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: USDC (USDC)
6 conflicts on slot 0x17606ba612…ea1b6e
Audit this contract →
← previous block·next block →recent activity