Block #72,859,380

← previous blocknext block →recent activity

Analyzing

Block #72,859,380

12 transactions · 12 stateful · 2026-05-06 18:08:36 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

1.33

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,859,380  ·  12 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xce7bfe5e…5e58

0x065c9d…c394

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x7f189cf6…afab

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x96cd1f8a…5351

0x065c9d…c394

5 touches
3 conflicts

0x42f7b53a…f7b4

0x065c9d…c394

5 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x3b8ffd61…f3ad

0x34b655…2a6f

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

15 conflicts on slot 0xce7bfe5ef1…205e58

← previous block·next block →recent activity