← previous blocknext block →recent activity

Analyzing

Block #111,666,698

30 transactions · 23 stateful · 2026-10-08 17:13:35 UTC

Parallelism

83/100

Blocked

22%

Avg conflicts / tx

0.47

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #111,666,698  ·  30 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x8c211514…b757

0x34b655…2a6f

4 touches
1 conflict

0xb4656137…5858

0x34b655…2a6f

4 touches
1 conflict

0xe6e1fa0c…bc92

0x34b655…2a6f

4 touches
1 conflict

0x4681609f…6493

0x34b655…2a6f

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x6235638c…643a

0x1b6862…e19c

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity