← previous blocknext block →recent activity
Analyzing
Block #105,931,208
25 transactions · 23 stateful · 2026-09-18 15:50:40 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.08
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,931,208 · 25 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
1w03w04w15w06w17w211w112w216w217w318w421w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb11940a…519b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x784d7a94…949c
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
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
10 conflicts on slot 0xdb11940a1f…24519b
Audit this contract →
← previous block·next block →recent activity