← previous blocknext block →recent activity
Analyzing
Block #106,207,731
24 transactions · 22 stateful · 2026-09-19 15:02:32 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
1.42
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,207,731 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w47w010w511w514w515w616w518w719w820w122w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa81592a3…f569
0x34b655…2a6f
10 touches
10 conflicts
0x712cfa71…2bf6
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x6d43ee99…bdda
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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
10 conflicts on slot 0xa81592a352…f9f569
Audit this contract →
← previous block·next block →recent activity