← previous blocknext block →recent activity

Analyzing

Block #74,915,661

20 transactions · 18 stateful · 2026-05-16 06:43:47 UTC

Parallelism

65/100

Blocked

56%

Avg conflicts / tx

1.4

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,915,661  ·  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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x0711ec2d…d973

0x34b655…2a6f

8 touches
6 conflicts

0x388e001a…7e04

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0x9be2b99a…a959

0x34b655…2a6f

8 touches
6 conflicts

0xd49762c9…1359

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: Perpl

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity