← previous blocknext block →recent activity

Analyzing

Block #73,014,538

17 transactions · 14 stateful · 2026-05-07 11:21:18 UTC

Parallelism

71/100

Blocked

29%

Avg conflicts / tx

0.41

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,014,538  ·  17 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

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0x28e46381…5a2a

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xc5c4c1d1…2145

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0003

0x5e60bc…fe22

2 touches
0 conflicts

0x00000000…0004

0x5e60bc…fe22

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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: 0x065c9d28…a9c394

3 conflicts on slot 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity