← previous blocknext block →recent activity

Analyzing

Block #74,351,862

34 transactions · 22 stateful · 2026-05-13 15:58:12 UTC

Parallelism

68/100

Blocked

59%

Avg conflicts / tx

1.24

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,351,862  ·  34 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

14 touches
21 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

14 touches
21 conflicts

0xf853eb8e…4027

0x34b655…2a6f

12 touches
15 conflicts

0x84143682…30a9

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xaebeea0e…875d

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x908d4442…2c4b

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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity