← previous blocknext block →recent activity
Analyzing
Block #106,801,416
22 transactions · 22 stateful · 2026-09-21 16:51:31 UTC
Parallelism
64/100
Blocked
68%
Avg conflicts / tx
2.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,801,416 · 22 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
1w02w13w24w37w08w09w210w111w212w313w414w516w219w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x5f8cac3a…8fc0
0x34b655…2a6f
10 touches
10 conflicts
0x6f5d7ccd…83d4
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c1
0x1b6862…e19c
8 touches
6 conflicts
0xbd9491f7…dd92
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity