← previous blocknext block →recent activity
Analyzing
Block #100,923,007
20 transactions · 18 stateful · 2026-09-01 02:28:55 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,923,007 · 20 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
1w04w15w210w011w112w213w314w419w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd884653…a6fd
0x065c9d…c394
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x0778475b…bd75
0x2a68ba…90c5
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xe27e6fd1…77a0
0x065c9d…c394
2 touches
0 conflicts
0xe27e6fd1…77a1
0x065c9d…c394
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: Kuru Exchange: Market-MON/USDC
10 conflicts on slot 0xfd88465360…84a6fd
Audit this contract →
← previous block·next block →recent activity