← previous blocknext block →recent activity
Analyzing
Block #100,920,123
21 transactions · 20 stateful · 2026-09-01 02:14:24 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,920,123 · 21 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
3w04w08w010w011w112w213w314w415w518w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x3fc02160…32cf
0x065c9d…c394
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x10a5a231…be40
0x34b655…2a6f
4 touches
1 conflict
0xc0b47739…26e5
0x065c9d…c394
4 touches
1 conflict
0x1fb8364c…c10d
0x34b655…2a6f
4 touches
1 conflict
0x2827ae77…4368
0x34b655…2a6f
4 touches
1 conflict
0x9d6a99f9…da64
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