← previous blocknext block →recent activity
Analyzing
Block #108,627,348
53 transactions · 47 stateful · 2026-09-28 02:04:35 UTC
Parallelism
66/100
Blocked
68%
Avg conflicts / tx
2.32
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #108,627,348 · 53 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w27w38w49w112w328w529w136w644w1145w1248w1551w652w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…001f
0x1b6862…e19c
14 touches
21 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
14 touches
21 conflicts
0xccf3cc00…a3dc
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x55a37f69…aece
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity