← previous blocknext block →recent activity
Analyzing
Block #106,282,239
41 transactions · 39 stateful · 2026-09-19 21:17:33 UTC
Parallelism
61/100
Blocked
72%
Avg conflicts / tx
2.9
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,282,239 · 41 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
1w02w13w24w35w46w28w011w312w416w517w518w619w724w825w833w337w439w640w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe4369ff…752e
0x34b655…2a6f
22 touches
55 conflicts
0x9ba10aad…9bc5
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
16 touches
28 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
10 touches
10 conflicts
0xe098738f…9bbe
0x34b655…2a6f
10 touches
10 conflicts
0xedd65b8e…c14c
0xd32edf…ff58
9 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
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
55 conflicts on slot 0xfe4369ff80…b5752e
Audit this contract →
← previous block·next block →recent activity