← previous blocknext block →recent activity
Analyzing
Block #106,040,175
111 transactions · 65 stateful · 2026-09-19 00:59:15 UTC
Parallelism
83/100
Blocked
77%
Avg conflicts / tx
2.4
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #106,040,175 · 111 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w010w011w012w117w218w320w421w522w623w724w434w537w139w843w979w280w381w182w192w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
34 touches
136 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xaad6be10…0801
0x2a68ba…90c5
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x886db264…846e
0x34b655…2a6f
12 touches
15 conflicts
0x65903ef9…2567
0x34b655…2a6f
12 touches
15 conflicts
0xd95357f7…6100
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
136 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity