← previous blocknext block →recent activity

Analyzing

Block #73,318,839

11 transactions · 8 stateful · 2026-05-08 21:05:59 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,318,839  ·  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

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xc96fb5ee…bbce

0x065c9d…c394

3 touches
1 conflict

0x80ed5040…7288

0x065c9d…c394

3 touches
1 conflict

0xb914894c…fcbc

0x065c9d…c394

3 touches
1 conflict

0x47c1a8e8…f74a

0x34b655…2a6f

2 touches
0 conflicts

0x81a10fb1…5d13

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

1 conflict on slot 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity