← previous blocknext block →recent activity
Analyzing
Block #106,934,029
28 transactions · 27 stateful · 2026-09-22 03:59:00 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.39
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,934,029 · 28 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
1w02w13w26w17w08w111w012w113w214w315w416w517w618w719w822w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
16 touches
28 conflicts
0x3780a34a…b50a
0x34b655…2a6f
14 touches
21 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0x7f27ad87…6498
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
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 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity