← previous blocknext block →recent activity
Analyzing
Block #106,916,425
30 transactions · 29 stateful · 2026-09-22 02:30:24 UTC
Parallelism
47/100
Blocked
76%
Avg conflicts / tx
3.9
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,916,425 · 30 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w310w411w512w613w714w815w916w1019w726w1327w1428w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51087f5a…61f7
0x34b655…2a6f
22 touches
55 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
20 touches
45 conflicts
0x409d2665…9192
0x34b655…2a6f
16 touches
28 conflicts
0x8469771e…1c75
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x803d32b5…8094
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
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
55 conflicts on slot 0x51087f5abf…f061f7
Audit this contract →
← previous block·next block →recent activity