← previous blocknext block →recent activity

Analyzing

Block #107,813,051

21 transactions · 18 stateful · 2026-09-25 05:45:54 UTC

Parallelism

76/100

Blocked

39%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,813,051  ·  21 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

0xba522812…1f1f

0x34b655…2a6f

10 touches
10 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x9ff4ca89…6115

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x0d0810b8…3720

0x34b655…2a6f

4 touches
1 conflict

0xe2995197…337c

0x860869…ff01

4 touches
1 conflict

0x3d93ad2c…e747

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 0xba52281226…3a1f1f

← previous block·next block →recent activity