← previous blocknext block →recent activity
Analyzing
Block #108,922,580
48 transactions · 39 stateful · 2026-09-29 02:54:06 UTC
Parallelism
56/100
Blocked
74%
Avg conflicts / tx
3.13
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #108,922,580 · 48 txs across 21 waves · depth 21
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
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w48w518w419w520w621w723w824w925w1026w1128w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
12 touches
15 conflicts
0xb035f967…ec60
0xd32edf…ff58
11 touches
15 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x15698ac9…2a46
0x34b655…2a6f
10 touches
10 conflicts
0x199a4f01…2183
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
78 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity