← previous blocknext block →recent activity
Analyzing
Block #100,919,383
20 transactions · 18 stateful · 2026-09-01 02:10:41 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,919,383 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w09w110w212w313w414w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x0778475b…bd75
0x2a68ba…90c5
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x13f70caf…5d7e
0x065c9d…c394
7 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
5 touches
3 conflicts
0x3040553c…5e28
0x754704…b603
4 touches
1 conflict
0x7391c293…d2d7
0x065c9d…c394
4 touches
1 conflict
0xe8e599f0…c8d8
0x065c9d…c394
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)
15 conflicts on slot 0xa1087a5ca6…0a66c4
Audit this contract →
← previous block·next block →recent activity