← previous blocknext block →recent activity

Analyzing

Block #74,457,238

9 transactions · 7 stateful · 2026-05-14 03:39:44 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,457,238  ·  9 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

0xd4765242…b852

0x065c9d…c394

4 touches
1 conflict

0x973634a8…68a1

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x07a3686c…9735

0x065c9d…c394

2 touches
0 conflicts

0x259188d8…d211

0x065c9d…c394

2 touches
0 conflicts

0x3a3e45b1…475c

0x065c9d…c394

2 touches
0 conflicts

0x3d4e48ba…ec8c

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

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 0xd476524276…e0b852

← previous block·next block →recent activity