← previous blocknext block →recent activity
Analyzing
Block #105,749,215
40 transactions · 36 stateful · 2026-09-18 00:32:24 UTC
Parallelism
65/100
Blocked
72%
Avg conflicts / tx
2.58
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #105,749,215 · 40 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w16w27w38w29w310w320w421w322w223w524w425w526w628w830w1032w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0x49890ced…6f23
0x34b655…2a6f
16 touches
28 conflicts
0x213b816c…a5e0
0x34b655…2a6f
14 touches
21 conflicts
0x3c6888af…a179
0x34b655…2a6f
14 touches
21 conflicts
0xdb1e37cb…90c9
0x34b655…2a6f
12 touches
15 conflicts
0x346bf59b…8fb6
0x34b655…2a6f
12 touches
15 conflicts
0x27034002…2f27
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
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
55 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity