← previous blocknext block →recent activity
Analyzing
Block #106,328,107
34 transactions · 27 stateful · 2026-09-20 01:08:22 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,328,107 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w19w111w013w214w215w016w117w218w319w420w521w626w327w333w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x65903ef9…2567
0x34b655…2a6f
12 touches
15 conflicts
0x48b24921…e45f
0x34b655…2a6f
10 touches
10 conflicts
0x4c0447dd…298b
0x34b655…2a6f
10 touches
10 conflicts
0x68292fe7…d918
0x34b655…2a6f
10 touches
10 conflicts
0x75f928fc…0465
0x34b655…2a6f
10 touches
10 conflicts
0x766c0128…5cb9
0x34b655…2a6f
10 touches
10 conflicts
0x9a291a56…9a9c
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity