← previous blocknext block →recent activity
Analyzing
Block #110,207,812
35 transactions · 30 stateful · 2026-10-03 14:47:03 UTC
Parallelism
54/100
Blocked
63%
Avg conflicts / tx
3.23
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #110,207,812 · 35 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w39w410w511w612w713w814w919w920w1023w928w1032w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
24 touches
66 conflicts
0xca841faa…486a
0x34b655…2a6f
22 touches
55 conflicts
0x3be6459e…270b
0x34b655…2a6f
20 touches
45 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
20 touches
45 conflicts
0x8b7e5c4e…5fae
0x34b655…2a6f
18 touches
36 conflicts
0x1032f16c…a9b1
0x34b655…2a6f
18 touches
36 conflicts
0x241b55d6…e0fa
0x34b655…2a6f
18 touches
36 conflicts
0x75f36d60…8556
0x34b655…2a6f
18 touches
36 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 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity