← previous blocknext block →recent activity

Analyzing

Block #73,499,636

21 transactions · 19 stateful · 2026-05-09 17:08:58 UTC

Parallelism

81/100

Blocked

32%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,499,636  ·  21 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

0x6d891c10…d066

0xd32edf…ff58

7 touches
6 conflicts

0xa4e3b3b1…0911

0x2a68ba…90c5

6 touches
3 conflicts

0x1c7a1fef…3ca8

0xa6afd3…d132

5 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6f

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

6 conflicts on slot 0x6d891c106f…b0d066

← previous block·next block →recent activity