← previous blocknext block →recent activity
Analyzing
Block #105,606,056
50 transactions · 44 stateful · 2026-09-17 12:31:49 UTC
Parallelism
66/100
Blocked
68%
Avg conflicts / tx
2.12
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,606,056 · 50 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w06w07w19w210w311w012w013w114w116w117w218w319w420w521w626w327w231w347w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb63ef486…0dcc
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
12 touches
15 conflicts
0xe3684e08…c96a
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xe22455da…1ce1
0x34b655…2a6f
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
28 conflicts on slot 0xb63ef48684…2d0dcc
Audit this contract →
← previous block·next block →recent activity