← previous blocknext block →recent activity
Analyzing
Block #100,924,134
13 transactions · 13 stateful · 2026-09-01 02:34:35 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,924,134 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w29w310w411w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x09193958…3415
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdd7ca9ce…9fdf
0x065c9d…c394
4 touches
1 conflict
0x82dd2252…e1ce
0x34b655…2a6f
2 touches
0 conflicts
0x9d6a99f9…da64
0x34b655…2a6f
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)
10 conflicts on slot 0xa1087a5ca6…0a66c4
Audit this contract →
← previous block·next block →recent activity