← previous blocknext block →recent activity

Analyzing

Block #74,920,440

40 transactions · 27 stateful · 2026-05-16 07:15:43 UTC

Parallelism

82/100

Blocked

56%

Avg conflicts / tx

1.15

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,920,440  ·  40 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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 conflicts

0xd49762c9…1359

0x34b655…2a6f

10 touches
10 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

10 touches
10 conflicts

0x3a65b271…34ab

0xd32edf…ff58

9 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x0711ec2d…d973

0x34b655…2a6f

8 touches
6 conflicts

0xcb45d9d6…cb85

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: 0x34b6552d…112a6f

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity