← previous blocknext block →recent activity
Analyzing
Block #106,957,066
23 transactions · 22 stateful · 2026-09-22 05:54:58 UTC
Parallelism
74/100
Blocked
59%
Avg conflicts / tx
1.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,957,066 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w28w010w111w212w313w414w515w117w318w419w120w222w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52b0b60a…f21e
0x34b655…2a6f
12 touches
15 conflicts
0x8590b692…b267
0x34b655…2a6f
10 touches
10 conflicts
0xa9988419…9f45
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x858e40c0…7e30
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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
15 conflicts on slot 0x52b0b60a1c…3ef21e
Audit this contract →
← previous block·next block →recent activity