← previous blocknext block →recent activity

Analyzing

Block #73,705,530

30 transactions · 24 stateful · 2026-05-10 16:05:46 UTC

Parallelism

80/100

Blocked

54%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,705,530  ·  30 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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x71e314f2…9ef7

0xd32edf…ff58

9 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x529acb6a…fcc6

0x065c9d…c394

8 touches
6 conflicts

0xaa8a1c54…ead3

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c4

0x1b6862…e19c

6 touches
3 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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity