← previous blocknext block →recent activity
Analyzing
Block #105,930,804
29 transactions · 23 stateful · 2026-09-18 15:48:38 UTC
Parallelism
66/100
Blocked
57%
Avg conflicts / tx
1.66
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,930,804 · 29 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w313w117w418w519w620w621w722w826w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x321da207…859d
0x34b655…2a6f
14 touches
21 conflicts
0xe796f8b7…ad55
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
8 touches
6 conflicts
0xdb11940a…519b
0x34b655…2a6f
6 touches
3 conflicts
0x56616d91…671f
0x34b655…2a6f
6 touches
3 conflicts
0x315e07b8…9823
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
21 conflicts on slot 0x321da20756…10859d
Audit this contract →
← previous block·next block →recent activity