← previous blocknext block →recent activity
Analyzing
Block #106,951,892
21 transactions · 20 stateful · 2026-09-22 05:28:56 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
1.43
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,951,892 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w310w413w417w518w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebb97840…6a07
0x34b655…2a6f
14 touches
21 conflicts
0xa9988419…9f45
0x34b655…2a6f
12 touches
15 conflicts
0x8f18c248…9da5
0x34b655…2a6f
10 touches
10 conflicts
0x7b8dd4b8…8aa7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
6 touches
3 conflicts
0x574628e9…dcc3
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
21 conflicts on slot 0xebb9784078…df6a07
Audit this contract →
← previous block·next block →recent activity