← previous blocknext block →recent activity
Analyzing
Block #105,841,583
21 transactions · 21 stateful · 2026-09-18 08:18:34 UTC
Parallelism
62/100
Blocked
57%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,841,583 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w113w214w315w416w517w618w719w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7be178f…2fb2
0x34b655…2a6f
16 touches
28 conflicts
0xb7ce83b1…2c96
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
10 touches
10 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
10 touches
10 conflicts
0xba5743c7…21c6
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
28 conflicts on slot 0xd7be178f26…dc2fb2
Audit this contract →
← previous block·next block →recent activity