← previous blocknext block →recent activity

Analyzing

Block #74,919,686

30 transactions · 22 stateful · 2026-05-16 07:10:41 UTC

Parallelism

77/100

Blocked

59%

Avg conflicts / tx

1.23

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,919,686  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x7f4d6557…930b

0xd32edf…ff58

11 touches
15 conflicts

0x10c19272…7444

0x1b6862…e19c

10 touches
10 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001d

0x1b6862…e19c

10 touches
10 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: 0x754704bc…afb603

15 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity