← previous blocknext block →recent activity

Analyzing

Block #73,483,308

9 transactions · 7 stateful · 2026-05-09 15:20:14 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,483,308  ·  9 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

0x7f430e47…4cbd

0x8d66a4…3095

4 touches
1 conflict

0xa91c899f…6ee3

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

0x1fcacf75…7ade

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xadd7a2bd…5f93

0x34b655…2a6f

2 touches
0 conflicts

0xb513632d…3b88

0x34b655…2a6f

2 touches
0 conflicts

0xc78b8610…8ca1

0x34b655…2a6f

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

1 conflict on slot 0x7f430e471f…4e4cbd

← previous block·next block →recent activity