← previous blocknext block →recent activity
Analyzing
Block #105,848,436
20 transactions · 19 stateful · 2026-09-18 08:53:12 UTC
Parallelism
50/100
Blocked
58%
Avg conflicts / tx
2.35
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,848,436 · 20 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
1w02w13w24w08w09w110w011w212w313w414w515w616w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62552a2a…7897
0x34b655…2a6f
18 touches
36 conflicts
0xdfce7dfe…5053
0x34b655…2a6f
14 touches
21 conflicts
0xc10b903d…2f54
0x34b655…2a6f
12 touches
15 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
10 touches
10 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0f94e353…1f32
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x62552a2af8…ff7897
Audit this contract →
← previous block·next block →recent activity