← previous blocknext block →recent activity
Analyzing
Block #110,393,405
23 transactions · 22 stateful · 2026-10-04 06:20:54 UTC
Parallelism
57/100
Blocked
55%
Avg conflicts / tx
1.35
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #110,393,405 · 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
1w02w13w24w310w011w012w113w214w315w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88710094…f3aa
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0053
0x1b6862…e19c
8 touches
6 conflicts
0x64e1f0ce…7158
0x1b6862…e19c
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
15 conflicts on slot 0x88710094d5…8cf3aa
Audit this contract →
← previous block·next block →recent activity