← previous blocknext block →recent activity

Analyzing

Block #74,764,997

20 transactions · 16 stateful · 2026-05-15 13:58:30 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.9

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,764,997  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf4eba309…cc7a

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x21d8e673…067b

0x1b6862…e19c

8 touches
6 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xe9b672ec…4cc1

0x065c9d…c394

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: 0xd32edf66…9fff58

10 conflicts on slot 0xf4eba309e7…fdcc7a

← previous block·next block →recent activity