← previous blocknext block →recent activity

Analyzing

Block #74,332,136

35 transactions · 28 stateful · 2026-05-13 13:47:05 UTC

Parallelism

71/100

Blocked

68%

Avg conflicts / tx

1.66

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,332,136  ·  35 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xa91c899f…6ee3

0x34b655…2a6f

10 touches
10 conflicts

0x0c5811ce…dfd8

0x34b655…2a6f

10 touches
10 conflicts

0x313f2565…5b00

0x34b655…2a6f

8 touches
6 conflicts

0x57de3828…3fbb

0x34b655…2a6f

8 touches
6 conflicts

0x886f7fe6…8b7a

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0x908d4442…2c4b

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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity