← previous blocknext block →recent activity

Analyzing

Block #73,391,171

16 transactions · 13 stateful · 2026-05-09 05:07:05 UTC

Parallelism

81/100

Blocked

23%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,391,171  ·  16 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

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xe038916c…b1be

0x2a68ba…90c5

4 touches
1 conflict

0x1b412965…8c0e

0x065c9d…c394

4 touches
1 conflict

0x757e2d5d…509e

0xd32edf…ff58

3 touches
1 conflict

0x09beabbc…065c

0x188d58…ea8e

2 touches
0 conflicts

0x09beabbc…065d

0x188d58…ea8e

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 0x4d87512b00…43897c

← previous block·next block →recent activity