← previous blocknext block →recent activity

Analyzing

Block #74,360,016

26 transactions · 21 stateful · 2026-05-13 16:52:28 UTC

Parallelism

58/100

Blocked

71%

Avg conflicts / tx

2.08

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,360,016  ·  26 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

0x62d080e9…4a7c

0x34b655…2a6f

16 touches
28 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0xc6417de0…2191

0xc8689a…ee79

12 touches
15 conflicts

0x57de3828…3fbb

0x34b655…2a6f

12 touches
15 conflicts

0x7b50a82b…f53d

0x34b655…2a6f

12 touches
15 conflicts

0x908d4442…2c4b

0x34b655…2a6f

12 touches
15 conflicts

0x99f080dc…58c1

0x34b655…2a6f

12 touches
15 conflicts

0xd49762c9…1359

0x34b655…2a6f

12 touches
15 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

28 conflicts on slot 0x62d080e928…5a4a7c

← previous block·next block →recent activity