← previous blocknext block →recent activity

Analyzing

Block #74,656,909

44 transactions · 31 stateful · 2026-05-15 01:56:51 UTC

Parallelism

80/100

Blocked

61%

Avg conflicts / tx

1.14

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,656,909  ·  44 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

0x06b54f35…8b17

0xd32edf…ff58

15 touches
28 conflicts

0xd5b10148…e631

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0028

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 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 0x06b54f35d7…688b17

← previous block·next block →recent activity