← previous blocknext block →recent activity
Analyzing
Block #107,979,008
20 transactions · 18 stateful · 2026-09-25 19:41:20 UTC
Parallelism
50/100
Blocked
61%
Avg conflicts / tx
1.65
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #107,979,008 · 20 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w27w310w411w512w613w714w815w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8c7dc95…c784
0x34b655…2a6f
14 touches
21 conflicts
0x2606abe5…3c4f
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x26bb6db7…f85e
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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: Perpl
21 conflicts on slot 0xc8c7dc95a0…01c784
Audit this contract →
← previous block·next block →recent activity