← previous blocknext block →recent activity

Analyzing

Block #74,420,889

35 transactions · 26 stateful · 2026-05-13 23:37:37 UTC

Parallelism

80/100

Blocked

58%

Avg conflicts / tx

1.17

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,420,889  ·  35 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

0xc3ce913f…599e

0xd32edf…ff58

13 touches
21 conflicts

0xd025d7d7…f05a

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

6 touches
3 conflicts

0x00f7e3b7…e016

0x188d58…ea8e

6 touches
3 conflicts

0xba5743c7…21c2

0x1b6862…e19c

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

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 0xc3ce913ff8…4e599e

← previous block·next block →recent activity