← previous blocknext block →recent activity
Analyzing
Block #105,843,723
34 transactions · 32 stateful · 2026-09-18 08:29:27 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
2.09
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,843,723 · 34 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
1w02w13w24w36w09w010w011w114w115w117w218w120w221w322w423w524w625w726w827w928w1033w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6d40b7f…2969
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0x2288c7e7…982a
0x34b655…2a6f
12 touches
15 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x05086df1…bd5a
0x34b655…2a6f
10 touches
10 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
8 touches
6 conflicts
0x198a4172…bc4f
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0xa6d40b7f0d…ff2969
Audit this contract →
← previous block·next block →recent activity