← previous blocknext block →recent activity

Analyzing

Block #74,406,787

7 transactions · 6 stateful · 2026-05-13 22:03:53 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,406,787  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x615736c7…d953

0x065c9d…c394

4 touches
1 conflict

0x689d5384…3d3d

0x065c9d…c394

3 touches
1 conflict

0x15fa256e…8eaf

0x065c9d…c394

2 touches
0 conflicts

0x3ac20dc5…896a

0x065c9d…c394

2 touches
0 conflicts

0xa91774a9…dc2c

0x065c9d…c394

2 touches
0 conflicts

0xb9c5fe9d…9a43

0x065c9d…c394

2 touches
0 conflicts

0xc0b9f7ae…d9dc

0x065c9d…c394

2 touches
0 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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity