← previous blocknext block →recent activity

Analyzing

Block #72,976,202

16 transactions · 14 stateful · 2026-05-07 07:06:08 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,976,202  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x92c60916…fe4d

0x065c9d…c394

4 touches
1 conflict

0x9c8c9939…2fb3

0x065c9d…c394

4 touches
1 conflict

0xaff64602…54ea

0x065c9d…c394

4 touches
1 conflict

0xf75d4b71…654a

0x065c9d…c394

4 touches
1 conflict

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

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 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity