← previous blocknext block →recent activity

Analyzing

Block #74,458,386

8 transactions · 7 stateful · 2026-05-14 03:47:22 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,458,386  ·  8 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x3acc2023…3ba4

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x00333293…c692

0x065c9d…c394

3 touches
1 conflict

0x72fb619a…b2c0

0x065c9d…c394

3 touches
1 conflict

0x8e90d4e2…f107

0x065c9d…c394

3 touches
1 conflict

0xdc85546c…9217

0x065c9d…c394

3 touches
1 conflict

0x4cea9514…fac7

0x065c9d…c394

2 touches
0 conflicts

0xebb6fd13…d56f

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

1 conflict on slot 0x3acc20233a…4d3ba4

← previous block·next block →recent activity