← previous blocknext block →recent activity
Analyzing
Block #106,923,846
26 transactions · 25 stateful · 2026-09-22 03:07:45 UTC
Parallelism
50/100
Blocked
72%
Avg conflicts / tx
2.46
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,923,846 · 26 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w08w19w010w111w212w313w414w516w617w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8590b692…b267
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
14 touches
21 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
14 touches
21 conflicts
0x681b1d0d…2e6b
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x81696049…331c
0x34b655…2a6f
12 touches
15 conflicts
0xb0f4f994…911e
0xd32edf…ff58
11 touches
15 conflicts
0xba5743c7…21c4
0x1b6862…e19c
10 touches
10 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 0x8590b69238…6ab267
Audit this contract →
← previous block·next block →recent activity