← previous blocknext block →recent activity
Analyzing
Block #100,879,601
30 transactions · 27 stateful · 2026-08-31 22:50:35 UTC
Parallelism
77/100
Blocked
37%
Avg conflicts / tx
0.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,879,601 · 30 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
1w02w13w24w07w110w211w312w413w514w618w019w028w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa994d0c4…65ca
0x065c9d…c394
12 touches
15 conflicts
0x0778475b…bd75
0x2a68ba…90c5
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x54e61177…f93a
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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: Kuru Exchange: Market-MON/USDC
15 conflicts on slot 0xa994d0c453…a165ca
Audit this contract →
← previous block·next block →recent activity