← previous blocknext block →recent activity
Analyzing
Block #106,016,260
24 transactions · 22 stateful · 2026-09-18 22:58:54 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,016,260 · 24 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
1w02w13w24w35w46w57w614w722w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
10 touches
10 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
10 touches
10 conflicts
0x238d0a65…428b
0x37db7f…ec7b
10 touches
10 conflicts
0xd3d054d7…4bfb
0x37db7f…ec7b
10 touches
10 conflicts
0x12e77486…ec2b
0x34b655…2a6f
10 touches
10 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
10 touches
10 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
10 touches
10 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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity