← previous blocknext block →recent activity

Analyzing

Block #73,921,770

29 transactions · 25 stateful · 2026-05-11 16:14:43 UTC

Parallelism

83/100

Blocked

48%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,921,770  ·  29 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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x86948c34…bd5e

0x34b655…2a6f

8 touches
6 conflicts

0xee230b20…5a0f

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xedb848fe…6534

0x34b655…2a6f

6 touches
3 conflicts

0x23951077…539b

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

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity