← previous blocknext block →recent activity

Analyzing

Block #74,765,466

39 transactions · 28 stateful · 2026-05-15 14:01:39 UTC

Parallelism

74/100

Blocked

75%

Avg conflicts / tx

1.44

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,765,466  ·  39 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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x443a3e47…f4a4

0x065c9d…c394

10 touches
10 conflicts

0x35074e28…b003

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002a

0x1b6862…e19c

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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity