← previous blocknext block →recent activity
Analyzing
Block #106,453,303
44 transactions · 43 stateful · 2026-09-20 11:38:30 UTC
Parallelism
61/100
Blocked
63%
Avg conflicts / tx
3.16
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,453,303 · 44 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w18w09w110w211w312w113w114w415w522w324w825w926w1027w1129w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9a6e112…69cc
0x34b655…2a6f
26 touches
78 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0x2aab0897…78f7
0x34b655…2a6f
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xf34802b3…9f10
0x1b6862…e19c
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
78 conflicts on slot 0xc9a6e112ce…9769cc
Audit this contract →
← previous block·next block →recent activity