← previous blocknext block →recent activity
Analyzing
Block #106,428,294
20 transactions · 20 stateful · 2026-09-20 09:32:34 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,428,294 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w18w010w111w212w313w414w515w618w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x8d664414…3344
0x34b655…2a6f
8 touches
6 conflicts
0x856fe446…d9dd
0x34b655…2a6f
8 touches
6 conflicts
0x2a6b4037…febd
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x172b0de5…980b
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity