← previous blocknext block →recent activity

Analyzing

Block #111,841,557

19 transactions · 16 stateful · 2026-10-09 07:53:24 UTC

Parallelism

89/100

Blocked

19%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #111,841,557  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xddd20e39…d524

0x34b655…2a6f

4 touches
1 conflict

0x84befb1f…6993

0x34b655…2a6f

4 touches
1 conflict

0x4d0178bf…8548

0x34b655…2a6f

4 touches
1 conflict

0x2bb0d58d…9dcf

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0x9d6a99f9…da64

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0xc824469a90…af6425

← previous block·next block →recent activity