← previous blocknext block →recent activity

Analyzing

Block #73,956,340

30 transactions · 18 stateful · 2026-05-11 20:04:41 UTC

Parallelism

73/100

Blocked

44%

Avg conflicts / tx

0.67

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,956,340  ·  30 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

0x16fbc996…a10d

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x4d42f16e…a6c8

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

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: 0xd32edf66…9fff58

15 conflicts on slot 0x16fbc996d7…42a10d

← previous block·next block →recent activity