← previous blocknext block →recent activity
Analyzing
Block #105,683,286
23 transactions · 19 stateful · 2026-09-17 19:00:36 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,683,286 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w111w012w113w214w015w217w218w319w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd6265424…0d3a
0x851145…3f07
8 touches
6 conflicts
0xc9327614…ba36
0x851145…3f07
8 touches
6 conflicts
0x35c68080…aace
0x851145…3f07
8 touches
6 conflicts
0x00000000…003d
0x851145…3f07
8 touches
6 conflicts
0x4213f1c0…219a
0x2a68ba…90c5
6 touches
3 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
6 touches
3 conflicts
0xf48fa71e…bb52
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity