← previous blocknext block →recent activity

Analyzing

Block #74,562,466

14 transactions · 14 stateful · 2026-05-14 15:25:31 UTC

Parallelism

71/100

Blocked

43%

Avg conflicts / tx

0.86

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,562,466  ·  14 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xe8805f31…806c

0x065c9d…c394

4 touches
1 conflict

0xae6a4c09…c78a

0x34b655…2a6f

4 touches
1 conflict

0xc799e56d…45aa

0x34b655…2a6f

4 touches
1 conflict

0x9fc59146…736c

0x34b655…2a6f

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0xe85e997b…bcf4

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity