← previous blocknext block →recent activity
Analyzing
Block #106,215,207
24 transactions · 24 stateful · 2026-09-19 15:40:10 UTC
Parallelism
54/100
Blocked
50%
Avg conflicts / tx
1.79
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,215,207 · 24 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
1w02w03w05w16w28w010w311w413w114w515w616w717w818w923w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xf00e711b…c539
0x34b655…2a6f
8 touches
6 conflicts
0x6ac9570f…7a27
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x71497cf1…0447
0x34b655…2a6f
8 touches
6 conflicts
0xf788c790…e66f
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity