← previous blocknext block →recent activity

Analyzing

Block #74,648,835

8 transactions · 7 stateful · 2026-05-15 01:02:47 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,648,835  ·  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

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x64caffa7…e4df

0x065c9d…c394

4 touches
1 conflict

0x43986f61…259f

0x065c9d…c394

3 touches
1 conflict

0x347c2e8c…6b3d

0x065c9d…c394

3 touches
1 conflict

0xc2f74db7…9883

0x065c9d…c394

3 touches
1 conflict

0x7592c6f5…2824

0x065c9d…c394

3 touches
1 conflict

0x9d1d9ccf…54ad

0x065c9d…c394

2 touches
0 conflicts

0xb8b0a31b…a3f1

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 0xffe431af56…838faa

← previous block·next block →recent activity