← previous blocknext block →recent activity
Analyzing
Block #106,281,806
30 transactions · 30 stateful · 2026-09-19 21:15:22 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
1.3
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,281,806 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w08w29w312w114w315w416w517w618w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ae7b171…b69f
0x34b655…2a6f
18 touches
36 conflicts
0xac0b4a08…faae
0x34b655…2a6f
12 touches
15 conflicts
0x5b6af007…0f35
0x34b655…2a6f
10 touches
10 conflicts
0xd911522b…e960
0x34b655…2a6f
8 touches
6 conflicts
0xe098738f…9bbe
0x34b655…2a6f
8 touches
6 conflicts
0xdaa004a9…041d
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
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 0x3ae7b1719e…e2b69f
Audit this contract →
← previous block·next block →recent activity