← previous blocknext block →recent activity

Analyzing

Block #111,676,707

20 transactions · 20 stateful · 2026-10-08 18:03:59 UTC

Parallelism

65/100

Blocked

40%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #111,676,707  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0xc9dd4373…6d99

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x3cf31547…051b

0x34b655…2a6f

4 touches
1 conflict

0x57054e87…d75a

0x34b655…2a6f

4 touches
1 conflict

0x724ba0cf…01c7

0x34b655…2a6f

4 touches
1 conflict

0x2982d270…c247

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity