← previous blocknext block →recent activity
Analyzing
Block #106,423,111
24 transactions · 22 stateful · 2026-09-20 09:06:29 UTC
Parallelism
83/100
Blocked
55%
Avg conflicts / tx
0.96
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,423,111 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w29w310w011w316w218w119w322w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cd9fd28…a158
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xd18a8dca…452c
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x7cd9fd286f…a7a158
Audit this contract →
← previous block·next block →recent activity