← previous blocknext block →recent activity

Analyzing

Block #73,505,198

17 transactions · 15 stateful · 2026-05-09 17:46:05 UTC

Parallelism

82/100

Blocked

27%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,505,198  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xc7bc364f…11dd

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x0a42f492…7385

0x065c9d…c394

2 touches
0 conflicts

0x12652408…6158

0x065c9d…c394

2 touches
0 conflicts

0x1de5c4a2…a3fc

0x065c9d…c394

2 touches
0 conflicts

0x3cbdea72…4bc5

0x065c9d…c394

2 touches
0 conflicts

0x5223fb6c…8dea

0x065c9d…c394

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

3 conflicts on slot 0xc7bc364fdc…c711dd

← previous block·next block →recent activity