← previous blocknext block →recent activity

Analyzing

Block #74,351,451

38 transactions · 25 stateful · 2026-05-13 15:55:28 UTC

Parallelism

84/100

Blocked

52%

Avg conflicts / tx

0.87

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,351,451  ·  38 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

0xe3684cd2…d5c3

0xd32edf…ff58

11 touches
15 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0xce8bbe33…b72e

0x3bd359…433a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x93afca4c…b479

0x1b6862…e19c

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 0xe3684cd216…43d5c3

← previous block·next block →recent activity