← previous blocknext block →recent activity
Analyzing
Block #105,925,136
35 transactions · 32 stateful · 2026-09-18 15:20:06 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.6
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,925,136 · 35 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w17w28w310w115w416w517w623w126w727w828w932w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x4089d428…b018
0x34b655…2a6f
10 touches
10 conflicts
0x0de7749d…5bef
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity