← previous blocknext block →recent activity

Analyzing

Block #74,458,728

11 transactions · 5 stateful · 2026-05-14 03:49:38 UTC

Parallelism

82/100

Blocked

20%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,458,728  ·  11 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

0x7a5bb1dd…69f0

0x065c9d…c394

4 touches
1 conflict

0xa0f88fab…fd4c

0x065c9d…c394

3 touches
1 conflict

0xa27ce053…e6f5

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0xb207cdff…b880

0x065c9d…c394

2 touches
0 conflicts

0xb6635423…a29d

0x065c9d…c394

2 touches
0 conflicts

0xb7587dbd…d4ea

0x065c9d…c394

2 touches
0 conflicts

0xff6b5651…df5e

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

1 conflict on slot 0x7a5bb1dd2d…1d69f0

← previous block·next block →recent activity