← previous blocknext block →recent activity
Analyzing
Block #106,931,890
35 transactions · 33 stateful · 2026-09-22 03:48:15 UTC
Parallelism
57/100
Blocked
64%
Avg conflicts / tx
2.31
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,931,890 · 35 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w010w011w112w213w315w416w517w618w719w820w921w1022w1123w1229w132w234w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04994ed2…9032
0x34b655…2a6f
20 touches
45 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
18 touches
36 conflicts
0x69168e33…6e1f
0x34b655…2a6f
18 touches
36 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
14 touches
21 conflicts
0x743f0e02…73ec
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x04994ed232…129032
Audit this contract →
← previous block·next block →recent activity