← previous blocknext block →recent activity

Analyzing

Block #73,263,221

12 transactions · 11 stateful · 2026-05-08 14:55:47 UTC

Parallelism

58/100

Blocked

36%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,263,221  ·  12 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

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x95a65edd…6896

0x065c9d…c394

3 touches
1 conflict

0x1388cebe…1f34

0x065c9d…c394

3 touches
1 conflict

0x37b78ef8…56da

0x065c9d…c394

3 touches
1 conflict

0x2f318a7e…401b

0x065c9d…c394

3 touches
1 conflict

0x9c98d98f…75fa

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity