← previous blocknext block →recent activity

Analyzing

Block #73,396,561

11 transactions · 10 stateful · 2026-05-09 05:43:00 UTC

Parallelism

55/100

Blocked

40%

Avg conflicts / tx

0.91

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,396,561  ·  11 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x0a42f492…7385

0x065c9d…c394

2 touches
0 conflicts

0x159faca1…491d

0x065c9d…c394

2 touches
0 conflicts

0x8227deb9…9922

0x065c9d…c394

2 touches
0 conflicts

0xa5e06609…b3f9

0x065c9d…c394

2 touches
0 conflicts

0xb0413fcd…6123

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity