← previous blocknext block →recent activity
Analyzing
Block #106,951,311
25 transactions · 23 stateful · 2026-09-22 05:26:00 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.84
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,951,311 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w27w38w09w012w113w216w318w521w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
12 touches
15 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x27025660…8303
0x34b655…2a6f
10 touches
10 conflicts
0x75e4cee9…0731
0x34b655…2a6f
10 touches
10 conflicts
0xc6a8c250…737e
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x49b9fdd5…9c16
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
15 conflicts on slot 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity