← previous blocknext block →recent activity

Analyzing

Block #74,565,970

43 transactions · 25 stateful · 2026-05-14 15:49:04 UTC

Parallelism

77/100

Blocked

56%

Avg conflicts / tx

1.21

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,565,970  ·  43 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

0xc23a2ded…e60a

0xd32edf…ff58

19 touches
45 conflicts

0x00000000…0000

0x1f86a9…17ed

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x0f94ee4c…189d

0x1b6862…e19c

6 touches
3 conflicts

0xb02fe354…948e

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xb02fe354…948e

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

45 conflicts on slot 0xc23a2ded68…f7e60a

← previous block·next block →recent activity