← previous blocknext block →recent activity

Analyzing

Block #74,237,587

36 transactions · 21 stateful · 2026-05-13 03:18:18 UTC

Parallelism

78/100

Blocked

62%

Avg conflicts / tx

1.14

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,237,587  ·  36 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

0xe85d933c…58e1

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xb6d6d740…e921

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0xf823e97f…2ee6

0x065c9d…c394

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

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 0xe85d933c92…3558e1

← previous block·next block →recent activity