← previous blocknext block →recent activity

Analyzing

Block #111,071,903

33 transactions · 30 stateful · 2026-10-06 15:19:12 UTC

Parallelism

85/100

Blocked

17%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #111,071,903  ·  33 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

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0xb75367ff…a2b7

0x34b655…2a6f

8 touches
6 conflicts

0x9a8ffdde…5644

0x34b655…2a6f

6 touches
3 conflicts

0x7dd96c96…7335

0x34b655…2a6f

6 touches
3 conflicts

0xddf10453…d774

0x34b655…2a6f

4 touches
1 conflict

0x29a58269…011a

0x34b655…2a6f

4 touches
1 conflict

0x53e08444…d671

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

← previous block·next block →recent activity