← previous blocknext block →recent activity

Analyzing

Block #73,026,836

18 transactions · 15 stateful · 2026-05-07 12:43:06 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

0.44

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,026,836  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0x9a95f678…0ab7

0xd32edf…ff58

5 touches
3 conflicts

0x4dd1db39…a995

0x188d58…ea8e

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0xe09eda07…8dda

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4dd1db39…a994

0x188d58…ea8e

4 touches
1 conflict

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

3 conflicts on slot 0x0b390c6160…02dc07

← previous block·next block →recent activity