← previous blocknext block →recent activity

Analyzing

Block #74,508,509

10 transactions · 8 stateful · 2026-05-14 09:21:25 UTC

Parallelism

80/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,508,509  ·  10 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

0x75e28443…b7e6

0x065c9d…c394

4 touches
1 conflict

0xeb9970ff…f21d

0x065c9d…c394

3 touches
1 conflict

0xdb9d90c4…7ded

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0283b7f6…f081

0x065c9d…c394

2 touches
0 conflicts

0x08a71964…186a

0x065c9d…c394

2 touches
0 conflicts

0x3ad1e24e…de94

0x065c9d…c394

2 touches
0 conflicts

0xae14798d…5b45

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 0x75e28443cb…26b7e6

← previous block·next block →recent activity