← previous blocknext block →recent activity
Analyzing
Block #105,608,841
21 transactions · 20 stateful · 2026-09-17 12:45:50 UTC
Parallelism
62/100
Blocked
60%
Avg conflicts / tx
1.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,608,841 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w18w19w211w312w413w514w615w616w719w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7ecbbe7…f713
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x28a8cc9b…db4c
0x34b655…2a6f
10 touches
10 conflicts
0x0c6c7007…e8f7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x953517cb…cdec
0x34b655…2a6f
6 touches
3 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
6 touches
3 conflicts
0xfc2493d3…6898
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
15 conflicts on slot 0xa7ecbbe767…04f713
Audit this contract →
← previous block·next block →recent activity