← previous blocknext block →recent activity

Analyzing

Block #74,430,576

35 transactions · 24 stateful · 2026-05-14 00:42:10 UTC

Parallelism

83/100

Blocked

67%

Avg conflicts / tx

1.03

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,430,576  ·  35 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf23ac660…a6b6

0xd32edf…ff58

11 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…001b

0x1b6862…e19c

8 touches
6 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

8 touches
6 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

8 touches
6 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf3d10975…0d07

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: 0xd32edf66…9fff58

15 conflicts on slot 0xf23ac66014…33a6b6

← previous block·next block →recent activity