← previous blocknext block →recent activity
Analyzing
Block #105,849,912
19 transactions · 17 stateful · 2026-09-18 09:00:37 UTC
Parallelism
47/100
Blocked
53%
Avg conflicts / tx
1.68
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,849,912 · 19 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
1w02w16w210w311w413w514w615w716w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc93877dc…f834
0x34b655…2a6f
16 touches
28 conflicts
0x23529e13…6f25
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb11d0fc9…04f6
0x34b655…2a6f
10 touches
10 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
8 touches
6 conflicts
0xc10b903d…2f54
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xcd5c0ecb…4b5f
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
28 conflicts on slot 0xc93877dc50…aef834
Audit this contract →
← previous block·next block →recent activity