← previous blocknext block →recent activity
Analyzing
Block #106,945,188
18 transactions · 18 stateful · 2026-09-22 04:55:11 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,945,188 · 18 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
1w02w13w24w06w27w38w49w313w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb30298c…1bf9
0x34b655…2a6f
12 touches
15 conflicts
0x858e40c0…7e30
0x34b655…2a6f
12 touches
15 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
10 touches
10 conflicts
0xab981df1…2941
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xd53220ed…4739
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x155e52ca…fac7
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
15 conflicts on slot 0xfb30298cd1…181bf9
Audit this contract →
← previous block·next block →recent activity