← previous blocknext block →recent activity

Analyzing

Block #74,649,089

18 transactions · 17 stateful · 2026-05-15 01:04:29 UTC

Parallelism

89/100

Blocked

35%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,649,089  ·  18 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

0xd89d2092…3265

0x754704…b603

4 touches
1 conflict

0x5ed383d5…204f

0x065c9d…c394

4 touches
1 conflict

0xbeeb7e93…e290

0x065c9d…c394

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0x00c73abe…ec87

0x754704…b603

4 touches
1 conflict

0x0e6eb255…76e5

0xd32edf…ff58

3 touches
1 conflict

0x1e31af19…4099

0x065c9d…c394

3 touches
1 conflict

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: 0x754704bc…afb603

1 conflict on slot 0xd89d209243…f53265

← previous block·next block →recent activity