← previous blocknext block →recent activity

Analyzing

Block #74,419,168

43 transactions · 24 stateful · 2026-05-13 23:26:13 UTC

Parallelism

79/100

Blocked

54%

Avg conflicts / tx

0.84

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,419,168  ·  43 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x66d78d3d…6750

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x5a3732cb…edaf

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x1c389468…6b0e

0x34b655…2a6f

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

28 conflicts on slot 0x66d78d3d60…206750

← previous block·next block →recent activity