← previous blocknext block →recent activity

Analyzing

Block #73,693,335

7 transactions · 6 stateful · 2026-05-10 14:43:30 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,693,335  ·  7 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

0xebc88bf3…b02a

0x065c9d…c394

4 touches
1 conflict

0xb3672d95…016c

0x065c9d…c394

3 touches
1 conflict

0xdc27f126…e209

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0ac31945…2c72

0x065c9d…c394

2 touches
0 conflicts

0x529acb6a…fcc6

0x065c9d…c394

2 touches
0 conflicts

0x55261ba9…464c

0x065c9d…c394

2 touches
0 conflicts

0x6848c89c…43d9

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 0xebc88bf3cf…6cb02a

← previous block·next block →recent activity