← previous blocknext block →recent activity
Analyzing
Block #106,301,369
35 transactions · 28 stateful · 2026-09-19 22:53:49 UTC
Parallelism
80/100
Blocked
61%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,301,369 · 35 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
1w03w04w07w18w19w010w111w215w216w317w418w319w421w522w630w431w434w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94dabb65…43a3
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x32c9c873…604c
0x34b655…2a6f
10 touches
10 conflicts
0xfadc118d…5d64
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x85a88798…f85e
0x34b655…2a6f
8 touches
6 conflicts
0x9a291a56…9a9c
0x34b655…2a6f
8 touches
6 conflicts
0x9f63b181…919d
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
10 conflicts on slot 0x94dabb6529…f943a3
Audit this contract →
← previous block·next block →recent activity