← previous blocknext block →recent activity

Analyzing

Block #73,751,826

16 transactions · 13 stateful · 2026-05-10 21:18:16 UTC

Parallelism

63/100

Blocked

38%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,751,826  ·  16 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

0xc6417de0…2191

0xc8689a…ee79

12 touches
15 conflicts

0x23951077…539b

0x34b655…2a6f

12 touches
15 conflicts

0x45b9e08c…a11b

0x34b655…2a6f

12 touches
15 conflicts

0x56a064ab…6c7d

0x34b655…2a6f

12 touches
15 conflicts

0x578e7f66…1b56

0x34b655…2a6f

12 touches
15 conflicts

0x57de3828…3fbb

0x34b655…2a6f

12 touches
15 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 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: 0xc8689a47…62ee79

15 conflicts on slot 0xc6417de023…802191

← previous block·next block →recent activity