← previous blocknext block →recent activity

Analyzing

Block #73,686,475

30 transactions · 25 stateful · 2026-05-10 13:57:18 UTC

Parallelism

87/100

Blocked

48%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,686,475  ·  30 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

0xa8297a66…40ee

0xd32edf…ff58

7 touches
6 conflicts

0xd49762c9…1359

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0xae69c125…2379

0x2a68ba…90c5

6 touches
3 conflicts

0x4f483049…3cc7

0x34b655…2a6f

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

6 touches
3 conflicts

0xaa8a1c54…ead3

0x34b655…2a6f

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: 0xd32edf66…9fff58

6 conflicts on slot 0xa8297a6668…0140ee

← previous block·next block →recent activity