← previous blocknext block →recent activity

Analyzing

Block #73,978,896

10 transactions · 9 stateful · 2026-05-11 22:35:18 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,978,896  ·  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

0x0ee25e11…97af

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x24a0fc17…c857

0x065c9d…c394

3 touches
1 conflict

0x4b41d6f2…b8c6

0xd32edf…ff58

3 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

2 touches
0 conflicts

0x322e3ed9…5542

0x065c9d…c394

2 touches
0 conflicts

0x4d5c964c…a25b

0x065c9d…c394

2 touches
0 conflicts

0x54638670…c819

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 0x0ee25e11fb…4797af

← previous block·next block →recent activity