← previous blocknext block →recent activity
Analyzing
Block #108,922,925
32 transactions · 24 stateful · 2026-09-29 02:55:50 UTC
Parallelism
69/100
Blocked
58%
Avg conflicts / tx
1.59
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,922,925 · 32 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
1w04w15w06w17w28w39w412w517w518w622w729w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002d
0x1b6862…e19c
14 touches
21 conflicts
0x6235638c…643b
0x1b6862…e19c
14 touches
21 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0xfb16d1ee…4490
0xd32edf…ff58
13 touches
21 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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity