← previous blocknext block →recent activity

Analyzing

Block #74,765,339

41 transactions · 29 stateful · 2026-05-15 14:00:47 UTC

Parallelism

76/100

Blocked

66%

Avg conflicts / tx

1.05

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,765,339  ·  41 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xd9852627…c004

0xd32edf…ff58

13 touches
21 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21c1

0x1b6862…e19c

8 touches
6 conflicts

0x4fbb8020…ce87

0x065c9d…c394

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd9f18d9a…141d

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

21 conflicts on slot 0xd985262724…79c004

← previous block·next block →recent activity