← previous blocknext block →recent activity

Analyzing

Block #74,587,170

30 transactions · 22 stateful · 2026-05-14 18:11:01 UTC

Parallelism

67/100

Blocked

59%

Avg conflicts / tx

1.4

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,587,170  ·  30 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

12 touches
15 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x83cde744…b76b

0x34b655…2a6f

10 touches
10 conflicts

0xaa6150bf…e946

0xd32edf…ff58

9 touches
10 conflicts

0xba5743c7…21c5

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity