← previous blocknext block →recent activity
Analyzing
Block #106,801,129
17 transactions · 16 stateful · 2026-09-21 16:50:05 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
1.18
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,801,129 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w08w19w010w111w212w313w414w015w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9edb7ad7…8d56
0x34b655…2a6f
8 touches
6 conflicts
0x774f21a1…340d
0x34b655…2a6f
8 touches
6 conflicts
0x9ce9d6a9…df50
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x8b41ec8f…c2d5
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 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 0x9edb7ad7f2…288d56
Audit this contract →
← previous block·next block →recent activity