← previous blocknext block →recent activity

Analyzing

Block #73,393,559

13 transactions · 9 stateful · 2026-05-09 05:23:00 UTC

Parallelism

62/100

Blocked

44%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,393,559  ·  13 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

0x4d87512b…897c

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x55cbfad1…61bb

0x065c9d…c394

3 touches
1 conflict

0x1ea46009…a0ce

0x065c9d…c394

2 touches
0 conflicts

0xd81a1719…9719

0x065c9d…c394

2 touches
0 conflicts

0xe69f65fd…8bc2

0x065c9d…c394

2 touches
0 conflicts

0xe6d55d00…ceb7

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

6 conflicts on slot 0x4d87512b00…43897c

← previous block·next block →recent activity