← previous blocknext block →recent activity
Analyzing
Block #105,869,305
24 transactions · 22 stateful · 2026-09-18 10:38:13 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,869,305 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w213w014w115w216w317w418w519w620w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fd0a899…4747
0x34b655…2a6f
14 touches
21 conflicts
0x80398c66…f3cc
0x34b655…2a6f
12 touches
15 conflicts
0x23529e13…6f25
0x34b655…2a6f
12 touches
15 conflicts
0x6771eae2…7014
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8968fc32…20e3
0x34b655…2a6f
8 touches
6 conflicts
0x8c4924be…a9b3
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
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
21 conflicts on slot 0x5fd0a89935…ac4747
Audit this contract →
← previous block·next block →recent activity