← previous blocknext block →recent activity
Analyzing
Block #106,053,177
25 transactions · 21 stateful · 2026-09-19 02:04:41 UTC
Parallelism
56/100
Blocked
57%
Avg conflicts / tx
1.28
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,053,177 · 25 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w212w313w414w515w616w717w821w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07c47b1c…93c8
0x34b655…2a6f
10 touches
10 conflicts
0x8dd36ab5…9da1
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x66b9c723…a1a0
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
8 touches
6 conflicts
0xd62f3741…b903
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0x07c47b1ce2…b693c8
Audit this contract →
← previous block·next block →recent activity