← previous blocknext block →recent activity

Analyzing

Block #74,452,523

32 transactions · 24 stateful · 2026-05-14 03:08:17 UTC

Parallelism

66/100

Blocked

63%

Avg conflicts / tx

1.78

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,452,523  ·  32 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

0xd98b3c10…67b8

0x34b655…2a6f

20 touches
45 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xfad189f8…96e6

0x1b6862…e19c

6 touches
3 conflicts

0x01737532…9b12

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

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

45 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity