← previous blocknext block →recent activity

Analyzing

Block #101,988,819

17 transactions · 16 stateful · 2026-09-04 19:55:14 UTC

Parallelism

76/100

Blocked

31%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,988,819  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe8114298…585b

0x34b655…2a6f

8 touches
6 conflicts

0x06897ca5…1495

0x34b655…2a6f

6 touches
3 conflicts

0x0efc7bb0…a8a1

0x34b655…2a6f

4 touches
1 conflict

0x33761f7c…8f85

0x34b655…2a6f

4 touches
1 conflict

0x3380282c…cf3c

0x34b655…2a6f

4 touches
1 conflict

0x3e7ad612…e804

0x34b655…2a6f

4 touches
1 conflict

0x4f3cc09a…2804

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

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

6 conflicts on slot 0xe81142982a…f0585b

← previous block·next block →recent activity