← previous blocknext block →recent activity

Analyzing

Block #74,555,921

32 transactions · 22 stateful · 2026-05-14 14:41:08 UTC

Parallelism

75/100

Blocked

45%

Avg conflicts / tx

0.84

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,555,921  ·  32 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0xd49762c9…1359

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0xf3d7a307…4d63

0x065c9d…c394

6 touches
3 conflicts

0xe9f42ee8…1f1c

0x34b655…2a6f

6 touches
3 conflicts

0x20ac0567…c954

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

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