← previous blocknext block →recent activity
Analyzing
Block #106,932,583
32 transactions · 30 stateful · 2026-09-22 03:51:44 UTC
Parallelism
63/100
Blocked
57%
Avg conflicts / tx
1.75
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,932,583 · 32 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w09w110w011w112w213w314w416w217w518w619w720w821w922w1023w1125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
18 touches
36 conflicts
0xc7b7704f…ab36
0x34b655…2a6f
16 touches
28 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0xd4230a60…bd13
0x34b655…2a6f
12 touches
15 conflicts
0xbbb93c5b…db1b
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x3a3097d7…2ab7
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity