← previous blocknext block →recent activity
Analyzing
Block #105,851,317
35 transactions · 30 stateful · 2026-09-18 09:07:41 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
1.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,851,317 · 35 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
1w02w13w24w37w218w419w520w325w426w528w629w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2521fcb3…3eac
0x34b655…2a6f
14 touches
21 conflicts
0xf7fa9b5c…4a8c
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0xb1526c23…f2bb
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 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 0x2521fcb351…0a3eac
Audit this contract →
← previous block·next block →recent activity