← previous blocknext block →recent activity

Analyzing

Block #74,410,436

23 transactions · 18 stateful · 2026-05-13 22:28:12 UTC

Parallelism

83/100

Blocked

50%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,410,436  ·  23 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

0x5c8c6ab6…dc36

0x065c9d…c394

8 touches
6 conflicts

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x6c6a1957…3524

0x065c9d…c394

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 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: 0x065c9d28…a9c394

6 conflicts on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity