← previous blocknext block →recent activity
Analyzing
Block #93,579,604
10 transactions · 8 stateful · 2026-08-06 07:57:44 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,579,604 · 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
1w02w13w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbcfed5b…96a6
0x754704…b603
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0e854949…baa7
0x754704…b603
4 touches
1 conflict
0x50be7f5d…2a30
0x754704…b603
4 touches
1 conflict
0xf60d5175…2d15
0x065c9d…c394
3 touches
1 conflict
0x4db23abc…0ac0
0x065c9d…c394
2 touches
0 conflicts
0x9ff176a9…152e
0x065c9d…c394
2 touches
0 conflicts
0xa9572f91…3155
0x065c9d…c394
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 0xcbcfed5bf3…4496a6
Audit this contract →
← previous block·next block →recent activity