← previous blocknext block →recent activity
Analyzing
Block #108,988,671
40 transactions · 32 stateful · 2026-09-29 08:28:19 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
2.17
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #108,988,671 · 40 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w27w08w19w110w211w312w413w514w615w717w818w919w1023w324w132w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
22 touches
55 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x5e28fb66…38cd
0x34b655…2a6f
10 touches
10 conflicts
0x7f5b2c1d…0e7f
0x34b655…2a6f
8 touches
6 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
8 touches
6 conflicts
0x8e99ff06…9eb5
0x34b655…2a6f
8 touches
6 conflicts
0xa6cb8d47…4f25
0x34b655…2a6f
8 touches
6 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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity