← previous blocknext block →recent activity

Analyzing

Block #74,510,735

38 transactions · 26 stateful · 2026-05-14 09:36:27 UTC

Parallelism

74/100

Blocked

58%

Avg conflicts / tx

1.11

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,510,735  ·  38 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

0x1dc86774…166a

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xf8f1e808…a4fd

0x34b655…2a6f

8 touches
6 conflicts

0xb017fbab…5580

0xd32edf…ff58

7 touches
6 conflicts

0x01737532…9b12

0x34b655…2a6f

7 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 0x1dc86774a8…36166a

← previous block·next block →recent activity