← previous blocknext block →recent activity

Analyzing

Block #73,046,456

13 transactions · 9 stateful · 2026-05-07 14:53:45 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,046,456  ·  13 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

0x0335ae80…8414

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ab

0x8d66a4…3095

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x082eaa9a…f72b

0x065c9d…c394

2 touches
0 conflicts

0x13595446…2bb7

0x065c9d…c394

2 touches
0 conflicts

0x19957dbf…bd44

0x065c9d…c394

2 touches
0 conflicts

0x32152ae2…ea65

0x065c9d…c394

2 touches
0 conflicts

0x674e778c…2ffb

0x065c9d…c394

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 0x0335ae8037…c18414

← previous block·next block →recent activity