← previous blocknext block →recent activity

Analyzing

Block #73,921,017

17 transactions · 16 stateful · 2026-05-11 16:09:43 UTC

Parallelism

71/100

Blocked

56%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,921,017  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xee230b20…5a0f

0x34b655…2a6f

10 touches
10 conflicts

0xd49762c9…1359

0x34b655…2a6f

8 touches
6 conflicts

0x8a85cf3d…2868

0x34b655…2a6f

8 touches
6 conflicts

0xac8e97a0…8426

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x9d652ee8…83ca

0x34b655…2a6f

8 touches
6 conflicts

0x2aef4269…ad47

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

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

10 conflicts on slot 0xee230b202a…c05a0f

← previous block·next block →recent activity