← previous blocknext block →recent activity

Analyzing

Block #73,751,480

23 transactions · 20 stateful · 2026-05-10 21:15:54 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1.26

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,751,480  ·  23 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x129ba946…48ab

0x34b655…2a6f

8 touches
6 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

8 touches
6 conflicts

0x99120c08…ee84

0x34b655…2a6f

8 touches
6 conflicts

0xaa0d0542…d8ec

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ad

0x8d66a4…3095

8 touches
6 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

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: Perpl

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity