← previous blocknext block →recent activity
Analyzing
Block #106,425,617
19 transactions · 19 stateful · 2026-09-20 09:19:05 UTC
Parallelism
58/100
Blocked
53%
Avg conflicts / tx
1.79
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,425,617 · 19 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
1w02w03w15w27w38w111w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedf0fd5d…0c8b
0x34b655…2a6f
16 touches
28 conflicts
0x7cd9fd28…a158
0x34b655…2a6f
10 touches
10 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
10 touches
10 conflicts
0x37ffbcf9…8f98
0x34b655…2a6f
10 touches
10 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
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
28 conflicts on slot 0xedf0fd5d3e…320c8b
Audit this contract →
← previous block·next block →recent activity