← previous blocknext block →recent activity

Analyzing

Block #73,493,273

28 transactions · 16 stateful · 2026-05-09 16:26:38 UTC

Parallelism

75/100

Blocked

38%

Avg conflicts / tx

0.61

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,493,273  ·  28 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xef7253a6…fe70

0xd32edf…ff58

11 touches
15 conflicts

0xd025d7d7…f05a

0x3bd359…433a

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0x76498d82…2995

0x000000…012a

2 touches
0 conflicts

0x3c02e4d1…494c

0x065c9d…c394

2 touches
0 conflicts

0x5a7b5146…7b50

0x065c9d…c394

2 touches
0 conflicts

0x4dd1db39…a994

0x188d58…ea8e

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

15 conflicts on slot 0xef7253a693…aefe70

← previous block·next block →recent activity