← previous blocknext block →recent activity

Analyzing

Block #74,454,749

20 transactions · 15 stateful · 2026-05-14 03:23:07 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

0.7

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,454,749  ·  20 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

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x313f2565…5b00

0x34b655…2a6f

8 touches
6 conflicts

0x45b9e08c…a11b

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

8 touches
6 conflicts

0x908d4442…2c4b

0x34b655…2a6f

8 touches
6 conflicts

0x9ec1983e…f08f

0x34b655…2a6f

8 touches
6 conflicts

0xc3aacf13…6b3d

0x34b655…2a6f

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: 0xc8689a47…62ee79

6 conflicts on slot 0xc6417de023…802191

← previous block·next block →recent activity