← previous blocknext block →recent activity

Analyzing

Block #74,351,331

30 transactions · 21 stateful · 2026-05-13 15:54:40 UTC

Parallelism

83/100

Blocked

43%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,351,331  ·  30 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

0xadb96516…5ada

0xd32edf…ff58

9 touches
10 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x0a6cb118…4ca4

0x1b6862…e19c

6 touches
3 conflicts

0x433e2a5b…638d

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0x1c354dc0…96de

0x754704…b603

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

10 conflicts on slot 0xadb9651651…2b5ada

← previous block·next block →recent activity