← previous blocknext block →recent activity
Analyzing
Block #105,851,814
34 transactions · 34 stateful · 2026-09-18 09:10:12 UTC
Parallelism
74/100
Blocked
68%
Avg conflicts / tx
2.09
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,851,814 · 34 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w610w014w115w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19db4c1d…a025
0x34b655…2a6f
14 touches
21 conflicts
0x5d500c4b…163c
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001f
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002f
0x1b6862…e19c
12 touches
15 conflicts
0x6aa624fd…a852
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x382434ca…96b5
0x34b655…2a6f
12 touches
15 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
21 conflicts on slot 0x19db4c1d49…b2a025
Audit this contract →
← previous block·next block →recent activity