← previous blocknext block →recent activity

Analyzing

Block #74,919,688

35 transactions · 30 stateful · 2026-05-16 07:10:42 UTC

Parallelism

66/100

Blocked

60%

Avg conflicts / tx

2.49

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,919,688  ·  35 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xdba87a32…b93a

0xd32edf…ff58

23 touches
66 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

12 touches
15 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002d

0x1b6862…e19c

8 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

66 conflicts on slot 0xdba87a32df…47b93a

← previous block·next block →recent activity