← previous blocknext block →recent activity
Analyzing
Block #107,805,380
18 transactions · 18 stateful · 2026-09-25 05:07:18 UTC
Parallelism
72/100
Blocked
61%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,805,380 · 18 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
1w02w13w24w05w06w17w28w39w412w113w214w116w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7d5acad…5158
0x40c49f…2af0
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xdbc6e634…e16c
0x1b6862…e19c
6 touches
3 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: 0x40c49f17…d22af0
10 conflicts on slot 0xc7d5acadd4…bf5158
Audit this contract →
← previous block·next block →recent activity