← previous blocknext block →recent activity

Analyzing

Block #73,261,597

17 transactions · 11 stateful · 2026-05-08 14:44:59 UTC

Parallelism

76/100

Blocked

27%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,261,597  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x4ca0a9e5…dee5

0xd32edf…ff58

5 touches
3 conflicts

0xbdff944d…447e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0xf7de6e5c…4ba4

0x065c9d…c394

3 touches
1 conflict

0x548b5ab0…8d6c

0x065c9d…c394

2 touches
0 conflicts

0x60904986…e706

0x065c9d…c394

2 touches
0 conflicts

0xbce2d6eb…5eea

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: 0xd32edf66…9fff58

3 conflicts on slot 0x4ca0a9e5c5…f7dee5

← previous block·next block →recent activity