← previous blocknext block →recent activity
Analyzing
Block #106,281,759
39 transactions · 37 stateful · 2026-09-19 21:15:08 UTC
Parallelism
56/100
Blocked
70%
Avg conflicts / tx
2.97
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,281,759 · 39 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
1w02w13w24w36w07w18w29w316w417w418w523w526w828w931w1235w1637w238w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbb571e4…6829
0x34b655…2a6f
20 touches
45 conflicts
0x1b25f260…c429
0x34b655…2a6f
16 touches
28 conflicts
0xad0e9509…895d
0x34b655…2a6f
14 touches
21 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
12 touches
15 conflicts
0x885efce3…7496
0x34b655…2a6f
12 touches
15 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
10 touches
10 conflicts
0x5503148f…9e4c
0x34b655…2a6f
10 touches
10 conflicts
0x8ce695ab…a7c8
0x34b655…2a6f
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 0xdbb571e456…b26829
Audit this contract →
← previous block·next block →recent activity