← previous blocknext block →recent activity

Analyzing

Block #74,218,230

15 transactions · 14 stateful · 2026-05-13 01:09:37 UTC

Parallelism

26/100

Blocked

71%

Avg conflicts / tx

3.53

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,218,230  ·  15 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

0x5de96bd3…c60c

0x34b655…2a6f

20 touches
45 conflicts

0xf853eb8e…4027

0x34b655…2a6f

20 touches
45 conflicts

0x99120c08…ee84

0x34b655…2a6f

18 touches
36 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

18 touches
36 conflicts

0xc6417de0…2191

0xc8689a…ee79

16 touches
28 conflicts

0x908d4442…2c4b

0x34b655…2a6f

16 touches
28 conflicts

0x99f080dc…58c1

0x34b655…2a6f

16 touches
28 conflicts

0xaa3492db…3703

0x34b655…2a6f

16 touches
28 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

45 conflicts on slot 0x5de96bd34a…ecc60c

← previous block·next block →recent activity