← previous blocknext block →recent activity

Analyzing

Block #74,346,710

11 transactions · 9 stateful · 2026-05-13 15:24:02 UTC

Parallelism

73/100

Blocked

44%

Avg conflicts / tx

0.55

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,346,710  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x4cfb9d2a…d768

0x065c9d…c394

2 touches
0 conflicts

0x52f24f17…0d88

0x065c9d…c394

2 touches
0 conflicts

0x805c56ed…a3a1

0x065c9d…c394

2 touches
0 conflicts

0x83e75a9f…5f0d

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