← previous blocknext block →recent activity
Analyzing
Block #106,535,793
21 transactions · 21 stateful · 2026-09-20 18:33:39 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,535,793 · 21 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
1w03w06w010w111w112w113w214w215w316w417w518w620w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f5a38d8…c230
0x34b655…2a6f
10 touches
10 conflicts
0x80fdc5be…7070
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x07c47b1c…93c8
0x34b655…2a6f
8 touches
6 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
8 touches
6 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe283e878…7262
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
10 conflicts on slot 0x8f5a38d868…2dc230
Audit this contract →
← previous block·next block →recent activity