← previous blocknext block →recent activity
Analyzing
Block #105,850,346
39 transactions · 39 stateful · 2026-09-18 09:02:48 UTC
Parallelism
64/100
Blocked
59%
Avg conflicts / tx
2.77
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #105,850,346 · 39 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w07w18w110w212w313w416w217w320w421w522w323w624w725w827w928w1030w1236w437w538w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc9915b5…542c
0x34b655…2a6f
22 touches
55 conflicts
0x3eb33a35…5bb4
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
12 touches
15 conflicts
0xd809bbec…baef
0x34b655…2a6f
12 touches
15 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 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
55 conflicts on slot 0xdc9915b513…2b542c
Audit this contract →
← previous block·next block →recent activity