← previous blocknext block →recent activity

Analyzing

Block #74,468,415

9 transactions · 7 stateful · 2026-05-14 04:54:04 UTC

Parallelism

56/100

Blocked

43%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,468,415  ·  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

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0ed87692…8bcc

0x065c9d…c394

2 touches
0 conflicts

0x18b33b3b…197f

0x065c9d…c394

2 touches
0 conflicts

0x865e0fbc…7641

0x065c9d…c394

2 touches
0 conflicts

0x8b0c6712…f2dc

0x065c9d…c394

2 touches
0 conflicts

0xae36c0f2…5479

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

3 conflicts on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity