← previous blocknext block →recent activity

Analyzing

Block #74,352,184

23 transactions · 19 stateful · 2026-05-13 16:00:20 UTC

Parallelism

61/100

Blocked

53%

Avg conflicts / tx

1.39

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,352,184  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x62d080e9…4a7c

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x111f72de…b33c

0x34b655…2a6f

8 touches
6 conflicts

0xfb790f01…fea9

0x34b655…2a6f

8 touches
6 conflicts

0x99f080dc…58c1

0x34b655…2a6f

6 touches
3 conflicts

0xd49762c9…1359

0x34b655…2a6f

6 touches
3 conflicts

0x37cfaf01…4a46

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 0x62d080e928…5a4a7c

← previous block·next block →recent activity