← previous blocknext block →recent activity
Analyzing
Block #106,923,337
25 transactions · 24 stateful · 2026-09-22 03:05:12 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,923,337 · 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
1w02w13w24w36w07w19w010w111w212w313w414w515w616w719w323w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23769ebc…c8ed
0x34b655…2a6f
10 touches
10 conflicts
0xab981df1…2941
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xa66499c2…9f47
0x34b655…2a6f
8 touches
6 conflicts
0x96784e2c…cb41
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x0c6e491f…1edb
0xd32edf…ff58
7 touches
6 conflicts
0xca841faa…486a
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 0x23769ebc9a…0ec8ed
Audit this contract →
← previous block·next block →recent activity