← previous blocknext block →recent activity

Analyzing

Block #74,498,354

43 transactions · 27 stateful · 2026-05-14 08:13:13 UTC

Parallelism

84/100

Blocked

63%

Avg conflicts / tx

0.93

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,498,354  ·  43 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

0xa907827f…6220

0xd32edf…ff58

11 touches
15 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

8 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x247c4899…e5ae

0x065c9d…c394

5 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 0xa907827f04…8e6220

← previous block·next block →recent activity