← previous blocknext block →recent activity
Analyzing
Block #106,216,975
26 transactions · 24 stateful · 2026-09-19 15:49:04 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,216,975 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w110w215w216w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60d709aa…4bdb
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
10 touches
10 conflicts
0xf00e711b…c539
0x34b655…2a6f
10 touches
10 conflicts
0x5e2ea201…12de
0x34b655…2a6f
8 touches
6 conflicts
0x1b554443…5402
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x1b3df55c…8693
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 0x60d709aa41…c54bdb
Audit this contract →
← previous block·next block →recent activity