← previous blocknext block →recent activity

Analyzing

Block #74,721,997

29 transactions · 20 stateful · 2026-05-15 09:10:51 UTC

Parallelism

76/100

Blocked

55%

Avg conflicts / tx

1.03

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,721,997  ·  29 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x150af51d…9c42

0x34b655…2a6f

10 touches
10 conflicts

0xa02838a3…bc54

0x34b655…2a6f

8 touches
6 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

8 touches
6 conflicts

0x773ae084…6b9d

0x34b655…2a6f

8 touches
6 conflicts

0x908d4442…2c4b

0x34b655…2a6f

6 touches
3 conflicts

0x99f080dc…58c1

0x34b655…2a6f

6 touches
3 conflicts

0xbea1a832…7b9c

0x34b655…2a6f

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity