← previous blocknext block →recent activity
Analyzing
Block #106,389,208
41 transactions · 41 stateful · 2026-09-20 06:15:52 UTC
Parallelism
59/100
Blocked
61%
Avg conflicts / tx
2.49
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,389,208 · 41 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
1w02w13w24w35w412w517w628w931w1032w1133w1234w1335w1336w1437w1538w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8cb0701…3926
0x34b655…2a6f
18 touches
36 conflicts
0x0ea037c0…1ff4
0x34b655…2a6f
18 touches
36 conflicts
0x2d071de0…c86e
0x34b655…2a6f
12 touches
15 conflicts
0xeab93ed3…e91b
0x34b655…2a6f
12 touches
15 conflicts
0xb363c4aa…07e0
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0xc8cb070152…393926
Audit this contract →
← previous block·next block →recent activity