← previous blocknext block →recent activity

Analyzing

Block #74,498,584

50 transactions · 31 stateful · 2026-05-14 08:14:44 UTC

Parallelism

80/100

Blocked

55%

Avg conflicts / tx

1.08

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,498,584  ·  50 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xe8e140eb…0dce

0xd32edf…ff58

15 touches
28 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

10 touches
10 conflicts

0xffe431af…8faa

0x065c9d…c394

10 touches
10 conflicts

0x6b1259e6…4e11

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001c

0x1b6862…e19c

10 touches
10 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 0xe8e140ebc7…3b0dce

← previous block·next block →recent activity