← previous blocknext block →recent activity

Analyzing

Block #73,204,863

17 transactions · 13 stateful · 2026-05-08 08:27:43 UTC

Parallelism

65/100

Blocked

54%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,204,863  ·  17 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

0x8a35acfb…d1ab

0x8d66a4…3095

6 touches
3 conflicts

0xa9988419…9f45

0x34b655…2a6f

6 touches
3 conflicts

0xe89e1a22…ce49

0x8d66a4…3095

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x374426df…f445

0xc8689a…ee79

6 touches
3 conflicts

0x143dba04…1b98

0x8d66a4…3095

4 touches
1 conflict

0x17cd1479…00bb

0x8d66a4…3095

4 touches
1 conflict

0x1e451306…7993

0x8d66a4…3095

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: 0x8d66a43f…113095

3 conflicts on slot 0x8a35acfbc1…6bd1ab

← previous block·next block →recent activity