← previous blocknext block →recent activity

Analyzing

Block #91,768,449

16 transactions · 15 stateful · 2026-07-31 00:06:03 UTC

Parallelism

50/100

Blocked

60%

Avg conflicts / tx

0.88

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #91,768,449  ·  16 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xda27c764…7fab

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002e

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c5

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 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

3 conflicts on slot 0xda27c76455…2e7fab

← previous block·next block →recent activity