← previous blocknext block →recent activity
Analyzing
Block #106,930,811
31 transactions · 30 stateful · 2026-09-22 03:42:49 UTC
Parallelism
58/100
Blocked
57%
Avg conflicts / tx
2.06
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,930,811 · 31 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w111w212w013w214w315w416w517w618w719w820w921w1022w1123w1226w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fad6fee…7714
0x34b655…2a6f
20 touches
45 conflicts
0x6b71b8f2…fc62
0x34b655…2a6f
16 touches
28 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
10 touches
10 conflicts
0x00216970…a965
0x34b655…2a6f
9 touches
10 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
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
45 conflicts on slot 0x5fad6fee64…277714
Audit this contract →
← previous block·next block →recent activity