← previous blocknext block →recent activity

Analyzing

Block #73,204,350

9 transactions · 8 stateful · 2026-05-08 08:24:17 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,204,350  ·  9 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xce7bfe5e…5e58

0x065c9d…c394

4 touches
1 conflict

0x10137e18…85e9

0x065c9d…c394

3 touches
1 conflict

0x01d0a492…3e9d

0x065c9d…c394

2 touches
0 conflicts

0x140d2741…268b

0x065c9d…c394

2 touches
0 conflicts

0x45af45d9…7647

0x065c9d…c394

2 touches
0 conflicts

0x60b068cd…ef82

0x065c9d…c394

2 touches
0 conflicts

0xb48a4f22…2da2

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 0x0000000000…00003d

← previous block·next block →recent activity