← previous blocknext block →recent activity
Analyzing
Block #106,470,869
38 transactions · 34 stateful · 2026-09-20 13:06:54 UTC
Parallelism
58/100
Blocked
62%
Avg conflicts / tx
3.11
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,470,869 · 38 txs across 16 waves · depth 16
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
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w18w214w120w322w423w224w525w626w727w828w929w1031w1233w1434w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c840894…764a
0x34b655…2a6f
24 touches
66 conflicts
0x911aed91…3a82
0x34b655…2a6f
16 touches
28 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
14 touches
21 conflicts
0xaa35a811…8c66
0x34b655…2a6f
12 touches
15 conflicts
0xcf49fa2d…69e2
0x34b655…2a6f
12 touches
15 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
10 touches
10 conflicts
0x67a56c8b…f955
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
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
66 conflicts on slot 0x1c84089465…17764a
Audit this contract →
← previous block·next block →recent activity