← previous blocknext block →recent activity
Analyzing
Block #106,198,321
37 transactions · 32 stateful · 2026-09-19 14:15:08 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,198,321 · 37 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
1w02w15w06w17w08w09w115w216w318w421w222w326w227w328w429w530w631w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fdb3ffb…6422
0x34b655…2a6f
16 touches
28 conflicts
0xd8cadc0d…776e
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x3643741b…109c
0x34b655…2a6f
8 touches
6 conflicts
0x366a19b0…f065
0x34b655…2a6f
8 touches
6 conflicts
0x68292fe7…d918
0x34b655…2a6f
8 touches
6 conflicts
0x6a9e408e…3721
0x34b655…2a6f
8 touches
6 conflicts
0xa3ff1ab2…8ae3
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
28 conflicts on slot 0x1fdb3ffbd7…776422
Audit this contract →
← previous block·next block →recent activity