← previous blocknext block →recent activity

Analyzing

Block #74,451,054

16 transactions · 10 stateful · 2026-05-14 02:58:29 UTC

Parallelism

88/100

Blocked

20%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,451,054  ·  16 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

0x337fcbd5…83e1

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x5b61a509…accb

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x3fb12dd2…cb8b

0x065c9d…c394

2 touches
0 conflicts

0x40aa6f63…80bd

0x065c9d…c394

2 touches
0 conflicts

0x8e3b383b…ea63

0x065c9d…c394

2 touches
0 conflicts

0xff3c13c8…0751

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 0x337fcbd54d…9583e1

← previous block·next block →recent activity