← previous blocknext block →recent activity

Analyzing

Block #74,311,687

8 transactions · 6 stateful · 2026-05-13 11:31:09 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,311,687  ·  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

0xa4725660…6ee3

0x065c9d…c394

4 touches
1 conflict

0xc1baee2f…9c73

0x065c9d…c394

3 touches
1 conflict

0xf7a4fb8f…7144

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0xbbee74c2…567a

0x065c9d…c394

2 touches
0 conflicts

0x3c223c30…06e6

0x1b6862…e19c

2 touches
0 conflicts

0xb02fe354…948e

0x1b6862…e19c

2 touches
0 conflicts

0xe28cdd07…4e6a

0x1b6862…e19c

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 0xa4725660f2…206ee3

← previous block·next block →recent activity