← previous blocknext block →recent activity

Analyzing

Block #74,332,187

33 transactions · 25 stateful · 2026-05-13 13:47:25 UTC

Parallelism

76/100

Blocked

72%

Avg conflicts / tx

1.61

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,332,187  ·  33 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

0x0ddf6db8…0561

0xd32edf…ff58

15 touches
28 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x17a7f697…dcb2

0x1b6862…e19c

10 touches
10 conflicts

0x313f2565…5b00

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

10 touches
10 conflicts

0xac8e97a0…8426

0x34b655…2a6f

10 touches
10 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

28 conflicts on slot 0x0ddf6db8cc…c40561

← previous block·next block →recent activity