← previous blocknext block →recent activity
Analyzing
Block #106,403,068
26 transactions · 24 stateful · 2026-09-20 07:25:37 UTC
Parallelism
39/100
Blocked
83%
Avg conflicts / tx
3.5
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,403,068 · 26 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
1w02w13w24w35w46w410w713w814w915w1016w1117w1018w1219w1320w1423w824w925w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd131fa…dbdb
0x34b655…2a6f
18 touches
36 conflicts
0x611a16a4…f6b1
0x34b655…2a6f
16 touches
28 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
12 touches
15 conflicts
0xc20bb2f9…b221
0x34b655…2a6f
10 touches
10 conflicts
0x6af2981e…5a35
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0xfdd131fae1…f8dbdb
Audit this contract →
← previous block·next block →recent activity