← previous blocknext block →recent activity

Analyzing

Block #74,915,329

7 transactions · 6 stateful · 2026-05-16 06:41:34 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,915,329  ·  7 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

0x388f889f…a655

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x510f1244…b5f4

0x065c9d…c394

2 touches
0 conflicts

0x5cc58846…f744

0x065c9d…c394

2 touches
0 conflicts

0x8d0f8a90…ad35

0x065c9d…c394

2 touches
0 conflicts

0xa3d9037d…389f

0x065c9d…c394

2 touches
0 conflicts

0xb5611a51…6d2e

0x065c9d…c394

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

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: 0x34b6552d…112a6f

1 conflict on slot 0x388f889f28…0aa655

← previous block·next block →recent activity