← previous blocknext block →recent activity

Analyzing

Block #74,334,201

41 transactions · 31 stateful · 2026-05-13 14:00:50 UTC

Parallelism

73/100

Blocked

68%

Avg conflicts / tx

2.15

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,334,201  ·  41 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

22 touches
55 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xc6417de0…2191

0xc8689a…ee79

14 touches
21 conflicts

0x908d4442…2c4b

0x34b655…2a6f

10 touches
10 conflicts

0x99f080dc…58c1

0x34b655…2a6f

10 touches
10 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0x9be2b99a…a959

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

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

55 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity