← previous blocknext block →recent activity
Analyzing
Block #100,923,243
20 transactions · 19 stateful · 2026-09-01 02:30:06 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,923,243 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w210w311w412w514w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x6daf7860…9bca
0x065c9d…c394
10 touches
10 conflicts
0x0778475b…bd75
0x2a68ba…90c5
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xcfe06a18…b5b5
0x34ae4d…3fc5
4 touches
1 conflict
0xd8fd2add…50fc
0x34ae4d…3fc5
4 touches
1 conflict
0x7e5ea60a…c4aa
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)
15 conflicts on slot 0xa1087a5ca6…0a66c4
Audit this contract →
← previous block·next block →recent activity