← previous blocknext block →recent activity

Analyzing

Block #73,200,242

11 transactions · 11 stateful · 2026-05-08 07:56:59 UTC

Parallelism

73/100

Blocked

27%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,200,242  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x5c1ca38a…261e

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8e66da19…66b6

0x065c9d…c394

4 touches
1 conflict

0x19b52c58…a6ab

0x065c9d…c394

3 touches
1 conflict

0x174017c6…90a4

0x065c9d…c394

3 touches
1 conflict

0x5f951062…bcd3

0x065c9d…c394

2 touches
0 conflicts

0x62eedf3c…6fdf

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 0x5c1ca38aae…2c261e

← previous block·next block →recent activity