← previous blocknext block →recent activity
Analyzing
Block #106,552,323
25 transactions · 23 stateful · 2026-09-20 19:56:50 UTC
Parallelism
56/100
Blocked
52%
Avg conflicts / tx
1.68
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,552,323 · 25 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
1w02w13w24w38w410w516w517w618w719w820w621w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xa22ea1ba…ea55
0x34b655…2a6f
14 touches
21 conflicts
0x21e79ad8…c5db
0x34b655…2a6f
8 touches
6 conflicts
0x2f50c84a…3640
0x34b655…2a6f
8 touches
6 conflicts
0x48828733…fd48
0x34b655…2a6f
8 touches
6 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
8 touches
6 conflicts
0xa57a72ed…64c2
0x34b655…2a6f
8 touches
6 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity