← previous blocknext block →recent activity

Analyzing

Block #74,032,750

6 transactions · 5 stateful · 2026-05-12 04:35:36 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,032,750  ·  6 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x5b94ba87…0f88

0xd32edf…ff58

3 touches
1 conflict

0x39b85263…3cd4

0x065c9d…c394

2 touches
0 conflicts

0x9519c9f7…bb1e

0x065c9d…c394

2 touches
0 conflicts

0xba3047ea…4069

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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 0x0000000000…00003d

← previous block·next block →recent activity