← previous blocknext block →recent activity

Analyzing

Block #74,482,458

10 transactions · 7 stateful · 2026-05-14 06:27:29 UTC

Parallelism

80/100

Blocked

29%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x7ed35b4d…36b8

0x065c9d…c394

4 touches
1 conflict

0xb64f2891…cf8c

0x065c9d…c394

4 touches
1 conflict

0xec91eabb…5d32

0x065c9d…c394

3 touches
1 conflict

0x84082be5…0ca5

0x065c9d…c394

3 touches
1 conflict

0x2c760e2d…833f

0x065c9d…c394

3 touches
1 conflict

0xdf25b393…32af

0x065c9d…c394

3 touches
1 conflict

0x5c01350e…ff57

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

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 0x7ed35b4d88…0736b8

← previous block·next block →recent activity