← previous blocknext block →recent activity

Analyzing

Block #74,773,140

35 transactions · 19 stateful · 2026-05-15 14:53:04 UTC

Parallelism

86/100

Blocked

58%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,773,140  ·  35 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

0xb1ad7ec7…32f6

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00c46468…f328

0x3bd359…433a

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

0x44ad89ba…cf83

0x5c2513…7777

6 touches
3 conflicts

0xce2b6650…ecc3

0x5c2513…7777

6 touches
3 conflicts

0x00000000…0000

0xcc67aa…c71c

6 touches
3 conflicts

0x00000000…0001

0xcc67aa…c71c

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

10 conflicts on slot 0xb1ad7ec768…6432f6

← previous block·next block →recent activity