← previous blocknext block →recent activity

Analyzing

Block #74,504,063

40 transactions · 28 stateful · 2026-05-14 08:51:29 UTC

Parallelism

75/100

Blocked

54%

Avg conflicts / tx

1.05

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,504,063  ·  40 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

0xfeca577e…2b6f

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x6b1259e6…4e11

0x1b6862…e19c

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x0824c484…d962

0x3bd359…433a

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 0xfeca577e50…712b6f

← previous block·next block →recent activity