← previous blocknext block →recent activity

Analyzing

Block #73,960,742

18 transactions · 7 stateful · 2026-05-11 20:33:53 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,960,742  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x9ea57326…329f

0x34b655…2a6f

6 touches
3 conflicts

0x20d070c8…c414

0x34b655…2a6f

4 touches
1 conflict

0x48f2292e…3ade

0x34b655…2a6f

4 touches
1 conflict

0xa3ff1ab2…8ae3

0x34b655…2a6f

4 touches
1 conflict

0xb6aedce9…a483

0x34b655…2a6f

4 touches
1 conflict

0xb8228d38…3953

0x34b655…2a6f

4 touches
1 conflict

0xcbf04108…7fb4

0x34b655…2a6f

4 touches
1 conflict

0x1b159f3d…9163

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x9ea57326ca…60329f

← previous block·next block →recent activity