← previous blocknext block →recent activity
Analyzing
Block #106,931,292
18 transactions · 17 stateful · 2026-09-22 03:45:14 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
1.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,931,292 · 18 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
1w02w13w26w07w18w29w310w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x155e52ca…fac7
0x34b655…2a6f
12 touches
15 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x8edc11b2…8a6f
0x34b655…2a6f
10 touches
10 conflicts
0x8dad7932…7029
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
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 0x155e52cae2…d8fac7
Audit this contract →
← previous block·next block →recent activity