← previous blocknext block →recent activity

Analyzing

Block #74,332,235

42 transactions · 27 stateful · 2026-05-13 13:47:44 UTC

Parallelism

76/100

Blocked

59%

Avg conflicts / tx

1.29

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,332,235  ·  42 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

18 touches
36 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

10 touches
10 conflicts

0x0711ec2d…d973

0x34b655…2a6f

8 touches
6 conflicts

0x99f080dc…58c1

0x34b655…2a6f

8 touches
6 conflicts

0x908d4442…2c4b

0x34b655…2a6f

8 touches
6 conflicts

0xa90e52fe…7eb1

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 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

36 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity