← previous blocknext block →recent activity
Analyzing
Block #106,109,309
25 transactions · 25 stateful · 2026-09-19 06:47:10 UTC
Parallelism
64/100
Blocked
56%
Avg conflicts / tx
1.8
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,109,309 · 25 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
1w02w13w04w15w26w37w48w59w610w713w114w221w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x735a86cd…b64d
0x34b655…2a6f
18 touches
36 conflicts
0xc20768f8…d947
0x34b655…2a6f
12 touches
15 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
10 touches
10 conflicts
0xf51ec09c…b4a9
0x34b655…2a6f
10 touches
10 conflicts
0xfd69dfe7…0bb7
0x34b655…2a6f
8 touches
6 conflicts
0x40226f40…3182
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
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
36 conflicts on slot 0x735a86cd19…53b64d
Audit this contract →
← previous block·next block →recent activity