← previous blocknext block →recent activity

Analyzing

Block #74,774,284

21 transactions · 19 stateful · 2026-05-15 15:00:44 UTC

Parallelism

67/100

Blocked

58%

Avg conflicts / tx

1.29

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,774,284  ·  21 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

0x0b0ad18f…73ad

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x765c236f…ff45

0x2a68ba…90c5

8 touches
6 conflicts

0x950e23fb…1f87

0x065c9d…c394

8 touches
6 conflicts

0x91220b8f…7a03

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

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: 0xd32edf66…9fff58

15 conflicts on slot 0x0b0ad18fb1…d373ad

← previous block·next block →recent activity