← previous blocknext block →recent activity
Analyzing
Block #106,242,267
25 transactions · 22 stateful · 2026-09-19 17:56:24 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,242,267 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w211w212w313w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c804088…250d
0x34b655…2a6f
8 touches
6 conflicts
0x159cff26…7665
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
8 touches
6 conflicts
0x55d48e94…6f58
0x34b655…2a6f
8 touches
6 conflicts
0xb2560305…f27d
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
6 conflicts on slot 0x6c804088db…bb250d
Audit this contract →
← previous block·next block →recent activity