← previous blocknext block →recent activity

Analyzing

Block #73,653,404

14 transactions · 14 stateful · 2026-05-10 10:14:04 UTC

Parallelism

79/100

Blocked

14%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,653,404  ·  14 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

0x8a35acfb…d1aa

0x8d66a4…3095

6 touches
3 conflicts

0xfff38d9f…7063

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a6

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a7

0x8d66a4…3095

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xcc6521c1…c892

0x8d66a4…3095

4 touches
1 conflict

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a9

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…6bd1aa

← previous block·next block →recent activity