← previous blocknext block →recent activity
Analyzing
Block #105,841,866
19 transactions · 19 stateful · 2026-09-18 08:20:00 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
1.84
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,841,866 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w08w310w111w212w313w414w515w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x5684aadd…8d62
0x34b655…2a6f
14 touches
21 conflicts
0xdb46e92a…d621
0x34b655…2a6f
12 touches
15 conflicts
0xc10b903d…2f54
0x34b655…2a6f
8 touches
6 conflicts
0xf66ca086…4535
0xd32edf…ff58
7 touches
6 conflicts
0xba5743c7…21c6
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity