← previous blocknext block →recent activity

Analyzing

Block #74,625,036

25 transactions · 19 stateful · 2026-05-14 22:24:19 UTC

Parallelism

64/100

Blocked

68%

Avg conflicts / tx

1.28

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,625,036  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xf3981be5…2c47

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

8 touches
6 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xacd10bf4…2244

0x34b655…2a6f

6 touches
3 conflicts

0x1fcacf75…7ade

0x34b655…2a6f

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 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

10 conflicts on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity