← previous blocknext block →recent activity

Analyzing

Block #74,711,476

14 transactions · 13 stateful · 2026-05-15 08:00:45 UTC

Parallelism

79/100

Blocked

31%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,711,476  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xd6aabe89…92f5

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…401e

0x34b655…2a6f

4 touches
1 conflict

0x10f5f4d8…572e

0x34b655…2a6f

2 touches
0 conflicts

0x1a693ae1…9d89

0x34b655…2a6f

2 touches
0 conflicts

0x23b2399c…6e4b

0x34b655…2a6f

2 touches
0 conflicts

0x5346ffe8…5894

0x34b655…2a6f

2 touches
0 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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity