← previous blocknext block →recent activity

Analyzing

Block #111,831,895

18 transactions · 17 stateful · 2026-10-09 07:04:47 UTC

Parallelism

78/100

Blocked

35%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #111,831,895  ·  18 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

0x4f363b3a…4b87

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb4656137…5858

0x34b655…2a6f

6 touches
3 conflicts

0x99601df7…7339

0x34b655…2a6f

6 touches
3 conflicts

0xf0f8cb61…fbbc

0x34b655…2a6f

4 touches
1 conflict

0x3355ee6d…4f6a

0x34b655…2a6f

4 touches
1 conflict

0x70d81211…f49f

0x34b655…2a6f

4 touches
1 conflict

0x8919c78e…7e9e

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

3 conflicts on slot 0x4f363b3a02…5c4b87

← previous block·next block →recent activity