← previous blocknext block →recent activity
Analyzing
Block #106,935,111
49 transactions · 46 stateful · 2026-09-22 04:04:27 UTC
Parallelism
65/100
Blocked
57%
Avg conflicts / tx
2.31
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,935,111 · 49 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
3w04w05w16w27w18w214w315w418w622w327w328w729w830w931w1040w1046w1447w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xe52f6f11…9a19
0x34b655…2a6f
16 touches
28 conflicts
0x469dac8d…3411
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
12 touches
15 conflicts
0x7fc8f46e…0f75
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x087bd8a7…5a10
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity