← previous blocknext block →recent activity

Analyzing

Block #106,207,610

23 transactions · 17 stateful · 2026-09-19 15:01:56 UTC

Parallelism

87/100

Blocked

29%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #106,207,610  ·  23 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x6a9e408e…3721

0x34b655…2a6f

6 touches
3 conflicts

0x77ed432f…fa04

0x065c9d…c394

4 touches
1 conflict

0x95523e2a…4c01

0x065c9d…c394

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x3643741b…109c

0x34b655…2a6f

4 touches
1 conflict

0x366a19b0…f065

0x34b655…2a6f

4 touches
1 conflict

0x5a37cc3f…4da8

0x34b655…2a6f

4 touches
1 conflict

0x68292fe7…d918

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x6a9e408e97…fb3721

← previous block·next block →recent activity