← previous blocknext block →recent activity
Analyzing
Block #105,853,241
31 transactions · 27 stateful · 2026-09-18 09:17:23 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
1.19
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,853,241 · 31 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
2w03w06w08w113w114w016w017w218w319w420w521w227w628w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc9915b5…542c
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x15c99322…6a62
0x34b655…2a6f
12 touches
15 conflicts
0xd911522b…e960
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf788c790…e66f
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x69941f7e…3b1d
0x34b655…2a6f
4 touches
1 conflict
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 0xdc9915b513…2b542c
Audit this contract →
← previous block·next block →recent activity