← previous blocknext block →recent activity

Analyzing

Block #74,711,560

27 transactions · 19 stateful · 2026-05-15 08:01:18 UTC

Parallelism

70/100

Blocked

53%

Avg conflicts / tx

0.74

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,711,560  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x92a6888a…469c

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x0747620e…977f

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

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 0x92a6888a49…f3469c

← previous block·next block →recent activity