← previous blocknext block →recent activity

Analyzing

Block #74,344,919

13 transactions · 12 stateful · 2026-05-13 15:12:05 UTC

Parallelism

69/100

Blocked

33%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,344,919  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x4f483049…3cc7

0x34b655…2a6f

8 touches
6 conflicts

0x5675c293…17d9

0x34b655…2a6f

8 touches
6 conflicts

0x5d70606a…1d53

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

8 touches
6 conflicts

0x908d4442…2c4b

0x34b655…2a6f

8 touches
6 conflicts

0xa009aa7b…a5ba

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