← previous blocknext block →recent activity
Analyzing
Block #107,823,197
22 transactions · 21 stateful · 2026-09-25 06:36:58 UTC
Parallelism
68/100
Blocked
62%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,823,197 · 22 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
1w02w13w24w36w07w18w29w012w113w214w315w416w217w518w619w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcd07321…1c31
0x34b655…2a6f
10 touches
10 conflicts
0x6d43ee99…bdda
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xf0b31448…b72a
0xd32edf…ff58
7 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x90a021f0…f922
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0xdcd0732149…7d1c31
Audit this contract →
← previous block·next block →recent activity