← previous blocknext block →recent activity
Analyzing
Block #107,443,406
25 transactions · 25 stateful · 2026-09-23 22:43:19 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,443,406 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w26w37w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1b1
0x37db7f…ec7b
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x39bc813f…59d0
0xd32edf…ff58
11 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
10 touches
10 conflicts
0x8a35acfb…d1b0
0x37db7f…ec7b
8 touches
6 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: 0x37db7fbf…3eec7b
21 conflicts on slot 0x8a35acfbc1…6bd1b1
Audit this contract →
← previous block·next block →recent activity