← previous blocknext block →recent activity
Analyzing
Block #106,957,522
53 transactions · 47 stateful · 2026-09-22 05:57:16 UTC
Parallelism
66/100
Blocked
70%
Avg conflicts / tx
3.11
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,957,522 · 53 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w210w412w113w222w223w324w325w426w527w428w529w642w643w1144w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
20 touches
45 conflicts
0x155e52ca…fac7
0x34b655…2a6f
18 touches
36 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
18 touches
36 conflicts
0x7efbf74f…f9d2
0x34b655…2a6f
14 touches
21 conflicts
0x858e40c0…7e30
0x34b655…2a6f
14 touches
21 conflicts
0x92f687cb…c1db
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 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
45 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity