← previous blocknext block →recent activity

Analyzing

Block #73,399,927

11 transactions · 7 stateful · 2026-05-09 06:05:27 UTC

Parallelism

82/100

Blocked

14%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,399,927  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xfff38d9f…7063

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ae

0x8d66a4…3095

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9538

0x188d58…ea8e

2 touches
0 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

2 touches
0 conflicts

0x1bc9b1ca…85ef

0x34b655…2a6f

2 touches
0 conflicts

0x34ea716f…4c40

0x34b655…2a6f

2 touches
0 conflicts

0x476615f7…2aaf

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 0xfff38d9fe2…647063

← previous block·next block →recent activity