← previous blocknext block →recent activity
Analyzing
Block #105,748,692
28 transactions · 25 stateful · 2026-09-18 00:29:46 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
1.93
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,748,692 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w08w09w110w215w316w417w420w121w522w623w724w827w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcadd9a74…8bb7
0x34b655…2a6f
16 touches
28 conflicts
0xcf4607b2…b7ca
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x43e3decb…be40
0x34b655…2a6f
10 touches
10 conflicts
0x1ec1cc66…7166
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xdaf02dea…dbd8
0x34b655…2a6f
8 touches
6 conflicts
0x3accf018…2e8b
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
28 conflicts on slot 0xcadd9a744b…3b8bb7
Audit this contract →
← previous block·next block →recent activity