← previous blocknext block →recent activity

Analyzing

Block #111,064,974

19 transactions · 17 stateful · 2026-10-06 14:44:11 UTC

Parallelism

74/100

Blocked

41%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #111,064,974  ·  19 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…0015

0x1b6862…e19c

6 touches
3 conflicts

0x261261a7…616e

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xdf613e47…1634

0xd32edf…ff58

5 touches
3 conflicts

0x7954ece9…fef0

0x34b655…2a6f

4 touches
1 conflict

0xb0b1d4bb…e250

0x34b655…2a6f

4 touches
1 conflict

0xb1599afe…fab0

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