← previous blocknext block →recent activity
Analyzing
Block #106,235,215
30 transactions · 28 stateful · 2026-09-19 17:20:55 UTC
Parallelism
60/100
Blocked
64%
Avg conflicts / tx
2.6
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,235,215 · 30 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w36w413w514w615w616w717w819w920w822w1023w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x160f9a70…b139
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x1a84e266…4f8a
0x34b655…2a6f
12 touches
15 conflicts
0xf254fe6c…8320
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x746bcce3…d0ce
0x34b655…2a6f
10 touches
10 conflicts
0x5906754f…b584
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
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
36 conflicts on slot 0x160f9a70df…14b139
Audit this contract →
← previous block·next block →recent activity