← previous blocknext block →recent activity

Analyzing

Block #73,653,660

17 transactions · 16 stateful · 2026-05-10 10:15:49 UTC

Parallelism

76/100

Blocked

44%

Avg conflicts / tx

0.76

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,653,660  ·  17 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

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x7cc95f42…a98f

0x065c9d…c394

4 touches
1 conflict

0x8d9b3b2b…134c

0x065c9d…c394

4 touches
1 conflict

0xf853eb8e…401e

0x34b655…2a6f

4 touches
1 conflict

0xa8bdf66d…7296

0x065c9d…c394

3 touches
1 conflict

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 0x0ac3194537…8f2c72

← previous block·next block →recent activity