← previous blocknext block →recent activity
Analyzing
Block #106,932,429
30 transactions · 30 stateful · 2026-09-22 03:50:57 UTC
Parallelism
50/100
Blocked
67%
Avg conflicts / tx
2.33
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,932,429 · 30 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w18w110w011w112w213w314w415w216w517w618w719w820w921w1022w324w1125w426w527w1228w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab981df1…2941
0x34b655…2a6f
16 touches
28 conflicts
0x39ff07cc…c1c5
0x34b655…2a6f
14 touches
21 conflicts
0x66774a98…88c8
0x34b655…2a6f
12 touches
15 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xec1dd684…b6b3
0x34b655…2a6f
10 touches
10 conflicts
0xea79e6d3…68ad
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 0xab981df1f6…082941
Audit this contract →
← previous block·next block →recent activity