← previous blocknext block →recent activity
Analyzing
Block #106,200,537
28 transactions · 26 stateful · 2026-09-19 14:26:17 UTC
Parallelism
61/100
Blocked
65%
Avg conflicts / tx
2.14
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,200,537 · 28 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w113w414w217w318w521w622w723w824w925w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10473e4f…cf84
0x34b655…2a6f
18 touches
36 conflicts
0x98568c43…ff4e
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
8 touches
6 conflicts
0x35b89cd8…5092
0x34b655…2a6f
8 touches
6 conflicts
0x05e1eba1…6491
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 0x10473e4faa…75cf84
Audit this contract →
← previous block·next block →recent activity