← previous blocknext block →recent activity

Analyzing

Block #74,668,707

35 transactions · 28 stateful · 2026-05-15 03:15:36 UTC

Parallelism

80/100

Blocked

71%

Avg conflicts / tx

1.49

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,668,707  ·  35 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

0x5c8c6ab6…dc36

0x065c9d…c394

12 touches
15 conflicts

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xffe431af…8faa

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0028

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21bf

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

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

15 conflicts on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity