← previous blocknext block →recent activity

Analyzing

Block #106,109,614

20 transactions · 18 stateful · 2026-09-19 06:48:42 UTC

Parallelism

65/100

Blocked

67%

Avg conflicts / tx

1.65

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,109,614  ·  20 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x735a86cd…b64d

0x34b655…2a6f

12 touches
15 conflicts

0x4fbd0a79…626a

0x34b655…2a6f

12 touches
15 conflicts

0xa829beb3…ef5e

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xe283e878…7262

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

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

15 conflicts on slot 0x735a86cd19…53b64d

← previous block·next block →recent activity