← previous blocknext block →recent activity

Analyzing

Block #106,542,065

20 transactions · 18 stateful · 2026-09-20 19:05:13 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,542,065  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xddd20e39…d524

0x34b655…2a6f

6 touches
3 conflicts

0x21d22421…0b7a

0x34b655…2a6f

4 touches
1 conflict

0x3643741b…109c

0x34b655…2a6f

4 touches
1 conflict

0x366a19b0…f065

0x34b655…2a6f

4 touches
1 conflict

0x38ad75de…7c1e

0x34b655…2a6f

4 touches
1 conflict

0x5a541bec…80fc

0x34b655…2a6f

4 touches
1 conflict

0xad862891…5d02

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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity