← previous blocknext block →recent activity
Analyzing
Block #110,380,920
24 transactions · 24 stateful · 2026-10-04 05:18:05 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
1.46
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #110,380,920 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w37w211w412w113w214w015w016w118w119w220w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x3b482aa4…6a1d
0x1b6862…e19c
10 touches
10 conflicts
0x091f0ff9…268a
0xd32edf…ff58
9 touches
10 conflicts
0x5bf53391…5c6b
0x1b6862…e19c
8 touches
6 conflicts
0x8efff96a…96fe
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity