← previous blocknext block →recent activity
Analyzing
Block #110,198,117
31 transactions · 27 stateful · 2026-10-03 13:58:17 UTC
Parallelism
42/100
Blocked
74%
Avg conflicts / tx
5.65
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #110,198,117 · 31 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w1222w1423w1326w1427w1528w1629w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
30 touches
105 conflicts
0xee97adde…06ab
0xd32edf…ff58
29 touches
105 conflicts
0x00000000…0015
0x1b6862…e19c
28 touches
91 conflicts
0x00000000…001e
0x1b6862…e19c
28 touches
91 conflicts
0x00000000…002e
0x1b6862…e19c
28 touches
91 conflicts
0x00000000…0040
0x1b6862…e19c
28 touches
91 conflicts
0x00000000…0057
0x1b6862…e19c
28 touches
91 conflicts
0x038d4614…c676
0x1b6862…e19c
28 touches
91 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
105 conflicts on slot 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity