← previous blocknext block →recent activity
Analyzing
Block #91,086,354
10 transactions · 9 stateful · 2026-07-28 14:52:21 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,086,354 · 10 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
3w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x636b0324…945e
0x7b9256…1fb2
4 touches
1 conflict
0x636b0324…945f
0x7b9256…1fb2
4 touches
1 conflict
0x636b0324…9462
0x7b9256…1fb2
4 touches
1 conflict
0x64f6df54…4258
0x7b9256…1fb2
4 touches
1 conflict
0x64f6df54…4259
0x7b9256…1fb2
4 touches
1 conflict
0xd98b3c10…67b8
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)
1 conflict on slot 0xe1f61186c5…67e2f8
Audit this contract →
← previous block·next block →recent activity