← previous blocknext block →recent activity
Analyzing
Block #106,200,506
27 transactions · 25 stateful · 2026-09-19 14:26:08 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,200,506 · 27 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
1w02w13w04w07w08w112w113w214w115w220w321w322w423w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb36c74c3…2567
0x34b655…2a6f
12 touches
15 conflicts
0xaa055b5a…1517
0x34b655…2a6f
10 touches
10 conflicts
0x7cf3eb0f…06c5
0x34b655…2a6f
8 touches
6 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd911522b…e960
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x4ec9ff52…e6f7
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
15 conflicts on slot 0xb36c74c3bc…ad2567
Audit this contract →
← previous block·next block →recent activity