← previous blocknext block →recent activity

Analyzing

Block #74,304,560

23 transactions · 16 stateful · 2026-05-13 10:43:41 UTC

Parallelism

78/100

Blocked

50%

Avg conflicts / tx

0.87

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,304,560  ·  23 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

0x4fa203c5…c5e6

0xd32edf…ff58

9 touches
10 conflicts

0xce8bbe33…b72e

0x3bd359…433a

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

8 touches
6 conflicts

0xf91b744e…9117

0x754704…b603

8 touches
6 conflicts

0x00000000…0028

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xd5b10148…e631

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

10 conflicts on slot 0x4fa203c5a3…e2c5e6

← previous block·next block →recent activity