← previous blocknext block →recent activity

Analyzing

Block #73,670,913

15 transactions · 10 stateful · 2026-05-10 12:12:10 UTC

Parallelism

80/100

Blocked

30%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,670,913  ·  15 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

0xad67c9bd…3fdf

0xd32edf…ff58

5 touches
3 conflicts

0x462c8be7…4f83

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ab

0x8d66a4…3095

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

2 touches
0 conflicts

0xa14be618…8a4d

0x065c9d…c394

2 touches
0 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x7cb2f3fa…4836

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: 0xd32edf66…9fff58

3 conflicts on slot 0xad67c9bd5f…8f3fdf

← previous block·next block →recent activity