← previous blocknext block →recent activity
Analyzing
Block #105,844,682
34 transactions · 34 stateful · 2026-09-18 08:34:17 UTC
Parallelism
56/100
Blocked
68%
Avg conflicts / tx
2.91
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #105,844,682 · 34 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w110w011w112w213w015w116w117w218w319w420w521w622w723w824w925w1030w1131w1232w1333w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
26 touches
78 conflicts
0xdfce7dfe…5053
0x34b655…2a6f
24 touches
66 conflicts
0x342dbb0b…1b19
0x34b655…2a6f
12 touches
15 conflicts
0x89999c15…fdac
0x34b655…2a6f
10 touches
10 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x2c0c3e3f…5849
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
78 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity