← previous blocknext block →recent activity

Analyzing

Block #74,730,827

44 transactions · 37 stateful · 2026-05-15 10:10:09 UTC

Parallelism

75/100

Blocked

78%

Avg conflicts / tx

1.75

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,730,827  ·  44 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x95c01e2c…2d8e

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0002

0xab3526…fa38

14 touches
21 conflicts

0x00000000…0012

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0019

0x1b6862…e19c

12 touches
15 conflicts

0x083a8763…5a79

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0029

0x1b6862…e19c

12 touches
15 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 0x95c01e2ca1…7d2d8e

← previous block·next block →recent activity