← previous blocknext block →recent activity
Analyzing
Block #108,918,893
49 transactions · 41 stateful · 2026-09-29 02:35:26 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
2.33
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #108,918,893 · 49 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w17w28w39w412w214w315w417w518w619w720w821w922w1024w1131w532w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
24 touches
66 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
14 touches
21 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
14 touches
21 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
12 touches
15 conflicts
0x3d59fbee…237e
0x34b655…2a6f
12 touches
15 conflicts
0x88fc2a68…3918
0x34b655…2a6f
12 touches
15 conflicts
0xada087b9…4aca
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 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
66 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity