← previous blocknext block →recent activity

Analyzing

Block #73,223,751

21 transactions · 18 stateful · 2026-05-08 10:33:24 UTC

Parallelism

76/100

Blocked

39%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,223,751  ·  21 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

0x020aa5d7…960e

0xd32edf…ff58

9 touches
10 conflicts

0x8d0dfe2c…3345

0x2a68ba…90c5

6 touches
3 conflicts

0xdb8c9583…afe9

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xd7ff8f4a…7729

0x065c9d…c394

3 touches
1 conflict

0x46cb45de…a567

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

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 0x020aa5d7ad…7a960e

← previous block·next block →recent activity