← previous blocknext block →recent activity

Analyzing

Block #74,921,228

27 transactions · 17 stateful · 2026-05-16 07:21:00 UTC

Parallelism

70/100

Blocked

53%

Avg conflicts / tx

1.26

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,921,228  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xf19bee4e…6ab5

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xba38536d…2b7d

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0012

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

0xba5743c7…21c4

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

28 conflicts on slot 0xf19bee4e49…836ab5

← previous block·next block →recent activity