← previous blocknext block →recent activity
Analyzing
Block #108,113,410
15 transactions · 14 stateful · 2026-09-26 06:57:39 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,113,410 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w512w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92f687cb…c1db
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
12 touches
15 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
12 touches
15 conflicts
0x75bb50cf…7e20
0xd32edf…ff58
11 touches
15 conflicts
0x5969523e…5191
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0x92f687cb06…bac1db
Audit this contract →
← previous block·next block →recent activity