← previous blocknext block →recent activity
Analyzing
Block #106,429,853
31 transactions · 27 stateful · 2026-09-20 09:40:24 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
1.77
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,429,853 · 31 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
1w02w13w24w36w012w013w114w115w216w219w320w421w522w623w724w828w329w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95063b48…269f
0x34b655…2a6f
16 touches
28 conflicts
0xba33378a…f1df
0x34b655…2a6f
12 touches
15 conflicts
0x1867b653…e61b
0x34b655…2a6f
10 touches
10 conflicts
0x2d071de0…c86e
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xea2d3331…6e34
0x1b6862…e19c
8 touches
6 conflicts
0x045532dd…4b7d
0x34b655…2a6f
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
28 conflicts on slot 0x95063b4883…9e269f
Audit this contract →
← previous block·next block →recent activity