← previous blocknext block →recent activity

Analyzing

Block #74,782,826

25 transactions · 22 stateful · 2026-05-15 15:57:48 UTC

Parallelism

72/100

Blocked

59%

Avg conflicts / tx

1.2

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,782,826  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001a

0x1b6862…e19c

10 touches
10 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x769c5066…280e

0xd32edf…ff58

9 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x8a5efe9a…fa31

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: 0x065c9d28…a9c394

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity