← previous blocknext block →recent activity
Analyzing
Block #108,919,135
23 transactions · 17 stateful · 2026-09-29 02:36:40 UTC
Parallelism
57/100
Blocked
59%
Avg conflicts / tx
1.57
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,919,135 · 23 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
1w02w13w28w311w316w017w418w519w620w721w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
8 touches
6 conflicts
0x247fdb78…cc97
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0056
0x1b6862…e19c
6 touches
3 conflicts
0x4e7eb462…b2af
0x1b6862…e19c
6 touches
3 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity