← previous blocknext block →recent activity
Analyzing
Block #105,869,794
25 transactions · 25 stateful · 2026-09-18 10:40:41 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,869,794 · 25 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
1w02w14w09w010w111w012w113w214w315w417w218w219w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa940e483…7146
0x34b655…2a6f
14 touches
21 conflicts
0x23529e13…6f25
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
10 touches
10 conflicts
0xd79c9727…1233
0x34b655…2a6f
8 touches
6 conflicts
0x297109ff…3754
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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 0xa940e48304…877146
Audit this contract →
← previous block·next block →recent activity