← previous blocknext block →recent activity

Analyzing

Block #74,774,282

33 transactions · 19 stateful · 2026-05-15 15:00:43 UTC

Parallelism

82/100

Blocked

58%

Avg conflicts / tx

0.64

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,774,282  ·  33 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x95a86ea8…0348

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x93afca4c…b47a

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x3e49348b…9445

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001a

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

10 conflicts on slot 0x95a86ea858…e20348

← previous block·next block →recent activity