← previous blocknext block →recent activity
Analyzing
Block #92,755,631
13 transactions · 11 stateful · 2026-08-03 10:52:24 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,755,631 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f03e539…f4cc
0x754704…b603
4 touches
1 conflict
0xe50f87d9…047c
0x754704…b603
4 touches
1 conflict
0x7aa512ae…d2e0
0x754704…b603
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0c119c6d…a42e
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2b621e3f…2156
0x34b655…2a6f
2 touches
0 conflicts
0x44614953…f05c
0x34b655…2a6f
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: USDC (USDC)
1 conflict on slot 0x7f03e53912…eef4cc
Audit this contract →
← previous block·next block →recent activity