← previous blocknext block →recent activity

Analyzing

Block #73,263,602

14 transactions · 12 stateful · 2026-05-08 14:58:19 UTC

Parallelism

86/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,263,602  ·  14 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

0xc2a8fca5…26a0

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0xcefc4ca3…0586

0x065c9d…c394

3 touches
1 conflict

0x76e3bb78…8b88

0x065c9d…c394

3 touches
1 conflict

0x07932efe…675c

0x065c9d…c394

2 touches
0 conflicts

0x0b390c61…dc07

0x065c9d…c394

2 touches
0 conflicts

0x4eba50ea…85b9

0x065c9d…c394

2 touches
0 conflicts

0x4f05cbbd…5d58

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: 0x065c9d28…a9c394

1 conflict on slot 0xc2a8fca50b…b826a0

← previous block·next block →recent activity