← previous blocknext block →recent activity
Analyzing
Block #106,930,890
37 transactions · 36 stateful · 2026-09-22 03:43:13 UTC
Parallelism
54/100
Blocked
78%
Avg conflicts / tx
2.76
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,930,890 · 37 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
1w02w13w24w35w46w07w18w09w010w111w212w313w414w515w616w718w129w430w532w233w335w236w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0463db49…5d05
0x34b655…2a6f
20 touches
45 conflicts
0xe7e580a2…39ed
0x34b655…2a6f
18 touches
36 conflicts
0x49890ced…6f23
0x34b655…2a6f
18 touches
36 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
18 touches
36 conflicts
0xf782ee27…41cd
0x34b655…2a6f
16 touches
28 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 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
45 conflicts on slot 0x0463db492b…795d05
Audit this contract →
← previous block·next block →recent activity