← previous blocknext block →recent activity

Analyzing

Block #74,351,478

33 transactions · 27 stateful · 2026-05-13 15:55:39 UTC

Parallelism

70/100

Blocked

59%

Avg conflicts / tx

1.73

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,351,478  ·  33 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

0xdaf2bd88…6813

0xd32edf…ff58

19 touches
45 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x511f46a7…eda9

0x1b6862…e19c

6 touches
3 conflicts

0xca36a439…0763

0x065c9d…c394

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

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

45 conflicts on slot 0xdaf2bd8859…c96813

← previous block·next block →recent activity