← previous blocknext block →recent activity

Analyzing

Block #73,571,418

21 transactions · 18 stateful · 2026-05-10 01:05:55 UTC

Parallelism

62/100

Blocked

44%

Avg conflicts / tx

1.29

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,571,418  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xa91c899f…6ee3

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x64e30b79…bc29

0x34b655…2a6f

8 touches
6 conflicts

0xd49762c9…1359

0x34b655…2a6f

6 touches
3 conflicts

0x7cbd466f…1700

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x1acaa26f…7b77

0x34b655…2a6f

6 touches
3 conflicts

0xc3aacf13…6b3d

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: 0x34b6552d…112a6f

15 conflicts on slot 0xa91c899f02…fa6ee3

← previous block·next block →recent activity