← previous blocknext block →recent activity

Analyzing

Block #74,510,253

33 transactions · 26 stateful · 2026-05-14 09:33:10 UTC

Parallelism

85/100

Blocked

50%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,510,253  ·  33 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

8 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0000

0x63e48b…53f2

8 touches
6 conflicts

0x00000000…0003

0x63e48b…53f2

8 touches
6 conflicts

0x00000000…0004

0x63e48b…53f2

8 touches
6 conflicts

0x9a555477…19a8

0x754704…b603

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity