← previous blocknext block →recent activity

Analyzing

Block #73,048,291

16 transactions · 11 stateful · 2026-05-07 15:05:59 UTC

Parallelism

81/100

Blocked

18%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,048,291  ·  16 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1a5

0x8d66a4…3095

4 touches
1 conflict

0x7f430e47…4cbd

0x8d66a4…3095

3 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9539

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…953a

0x188d58…ea8e

2 touches
0 conflicts

0xe1d46c51…3ad4

0x188d58…ea8e

2 touches
0 conflicts

0xe1d46c51…3ad5

0x188d58…ea8e

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: 0x34b6552d…112a6f

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity