← previous blocknext block →recent activity
Analyzing
Block #94,251,904
10 transactions · 8 stateful · 2026-08-08 16:24:15 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,251,904 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x61dbc097…40aa
0x34b655…2a6f
4 touches
1 conflict
0xbec23443…9293
0x34b655…2a6f
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x7e8c32fc…6465
0x065c9d…c394
3 touches
1 conflict
0x5c27f72f…c18f
0x065c9d…c394
3 touches
1 conflict
0x8da8e5ff…d5ab
0x34b655…2a6f
3 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 0xa1087a5ca6…0a66c4
Audit this contract →
← previous block·next block →recent activity