← previous blocknext block →recent activity

Analyzing

Block #74,041,616

10 transactions · 8 stateful · 2026-05-12 05:34:34 UTC

Parallelism

80/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,041,616  ·  10 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xdaca243a…f9de

0x34b655…2a6f

4 touches
1 conflict

0x57cfcfe6…b0a1

0x065c9d…c394

4 touches
1 conflict

0x1ec9de9c…0c1f

0x065c9d…c394

2 touches
0 conflicts

0x45e1d857…4eab

0x065c9d…c394

2 touches
0 conflicts

0x588295f1…308e

0x065c9d…c394

2 touches
0 conflicts

0x92fd553b…f345

0x065c9d…c394

2 touches
0 conflicts

0x9758a71b…2438

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 0x0000000000…00003d

← previous block·next block →recent activity