← previous blocknext block →recent activity

Analyzing

Block #74,429,067

9 transactions · 8 stateful · 2026-05-14 00:32:06 UTC

Parallelism

56/100

Blocked

38%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,429,067  ·  9 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x1242be42…f041

0x065c9d…c394

4 touches
1 conflict

0x1499f925…f32c

0x065c9d…c394

4 touches
1 conflict

0xa24ec71d…5d18

0x065c9d…c394

3 touches
1 conflict

0x63163465…6bb1

0x065c9d…c394

3 touches
1 conflict

0x73c066b0…3647

0x065c9d…c394

3 touches
1 conflict

0x2e2214a9…fe0d

0x5d823e…89c6

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity