← previous blocknext block →recent activity

Analyzing

Block #74,454,276

26 transactions · 18 stateful · 2026-05-14 03:19:57 UTC

Parallelism

77/100

Blocked

50%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,454,276  ·  26 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x1c389468…6b0e

0x34b655…2a6f

10 touches
10 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

8 touches
6 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe3d8c921…3d15

0x34b655…2a6f

6 touches
3 conflicts

0xbed60ae3…a19c

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

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: 0x34b6552d…112a6f

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity