← previous blocknext block →recent activity

Analyzing

Block #73,443,727

12 transactions · 10 stateful · 2026-05-09 10:56:52 UTC

Parallelism

67/100

Blocked

30%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,443,727  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x1f204c52…e21e

0x0555e3…2b9c

2 touches
0 conflicts

0x64f7e225…80ce

0x0555e3…2b9c

2 touches
0 conflicts

0x8b3f3eb2…7ee1

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0008

0xc9bec7…f5d5

2 touches
0 conflicts

0x00000000…0009

0xc9bec7…f5d5

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 0x0000000000…00003d

← previous block·next block →recent activity