← previous blocknext block →recent activity
Analyzing
Block #106,452,619
23 transactions · 23 stateful · 2026-09-20 11:35:03 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,452,619 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w08w09w110w212w313w414w515w619w020w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xf2d034de…f617
0x34b655…2a6f
8 touches
6 conflicts
0x8d664414…3344
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
6 touches
3 conflicts
0x176a8d88…fb6a
0x34b655…2a6f
6 touches
3 conflicts
0x30ae635d…5e67
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity