← previous blocknext block →recent activity

Analyzing

Block #73,867,387

18 transactions · 13 stateful · 2026-05-11 10:12:28 UTC

Parallelism

72/100

Blocked

54%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,867,387  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xbb711218…8914

0xd32edf…ff58

9 touches
10 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x9fbf88eb…fbc4

0x065c9d…c394

5 touches
3 conflicts

0x489cb750…7069

0x065c9d…c394

4 touches
1 conflict

0xa33d2a71…3591

0x754704…b603

4 touches
1 conflict

0x3ea94fdc…ad7a

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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

10 conflicts on slot 0xbb711218ba…0f8914

← previous block·next block →recent activity