← previous blocknext block →recent activity
Analyzing
Block #106,934,998
41 transactions · 36 stateful · 2026-09-22 04:03:53 UTC
Parallelism
76/100
Blocked
64%
Avg conflicts / tx
1.88
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,934,998 · 41 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w07w18w09w111w012w113w114w215w316w218w319w420w521w625w226w328w329w430w431w532w734w938w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x469dac8d…3411
0x34b655…2a6f
16 touches
28 conflicts
0xf7b76d2f…1b9c
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x6a9340ab…27b4
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x087bd8a7…5a10
0x34b655…2a6f
10 touches
10 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
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
28 conflicts on slot 0x469dac8dcd…223411
Audit this contract →
← previous block·next block →recent activity