← previous blocknext block →recent activity

Analyzing

Block #73,986,678

7 transactions · 7 stateful · 2026-05-11 23:27:39 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,986,678  ·  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

0x2b88e1be…8d11

0x065c9d…c394

4 touches
1 conflict

0xf62d4046…1e62

0x065c9d…c394

3 touches
1 conflict

0x61873424…62df

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x6d09a421…50b7

0x065c9d…c394

2 touches
0 conflicts

0x98103e5c…f3f5

0x065c9d…c394

2 touches
0 conflicts

0xa1e3bb53…eff7

0x065c9d…c394

2 touches
0 conflicts

0xfcfbffe7…db7a

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 0x2b88e1be20…088d11

← previous block·next block →recent activity