← previous blocknext block →recent activity
Analyzing
Block #106,422,782
24 transactions · 24 stateful · 2026-09-20 09:04:49 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
2.38
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,422,782 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w09w110w217w418w519w620w721w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8e6ca49…a0f6
0x34b655…2a6f
18 touches
36 conflicts
0x05b1f4af…b126
0x34b655…2a6f
16 touches
28 conflicts
0xfc24540b…6463
0x34b655…2a6f
14 touches
21 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0xd53220ed…4737
0x1b6862…e19c
10 touches
10 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
36 conflicts on slot 0xe8e6ca4971…0ca0f6
Audit this contract →
← previous block·next block →recent activity