← previous blocknext block →recent activity

Analyzing

Block #74,232,035

8 transactions · 6 stateful · 2026-05-13 02:41:23 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,232,035  ·  8 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

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7882d829…8862

0xd32edf…ff58

3 touches
1 conflict

0x0d57388f…e430

0x065c9d…c394

2 touches
0 conflicts

0x20e96ba5…3cda

0x065c9d…c394

2 touches
0 conflicts

0x613e0d6f…f220

0x065c9d…c394

2 touches
0 conflicts

0xaa70897b…95b5

0x065c9d…c394

2 touches
0 conflicts

0xb785c037…2a6e

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 0xcf3283bab2…c3c9fa

← previous block·next block →recent activity