← previous blocknext block →recent activity

Analyzing

Block #73,648,782

10 transactions · 9 stateful · 2026-05-10 09:42:58 UTC

Parallelism

40/100

Blocked

56%

Avg conflicts / tx

1.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,648,782  ·  10 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb159af88…a9e7

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x9af5e0d9…319e

0x065c9d…c394

4 touches
2 conflicts

0xd1fd2fe6…56a7

0x065c9d…c394

3 touches
1 conflict

0xc1fadb10…4256

0x065c9d…c394

2 touches
0 conflicts

0xd213fdf8…46ee

0x065c9d…c394

2 touches
0 conflicts

0xd57629e2…3219

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

15 conflicts on slot 0xb159af880b…47a9e7

← previous block·next block →recent activity