← previous blocknext block →recent activity
Analyzing
Block #106,931,318
15 transactions · 15 stateful · 2026-09-22 03:45:22 UTC
Parallelism
60/100
Blocked
67%
Avg conflicts / tx
1.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,931,318 · 15 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
1w02w13w24w05w36w07w18w29w310w412w413w314w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6deafb5…5c25
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xa4abfa3b…89a7
0xd32edf…ff58
9 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0xabfdd966…a0e7
0x34b655…2a6f
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
10 conflicts on slot 0xf6deafb553…9e5c25
Audit this contract →
← previous block·next block →recent activity