← previous blocknext block →recent activity

Analyzing

Block #72,571,031

18 transactions · 15 stateful · 2026-05-05 10:06:11 UTC

Parallelism

72/100

Blocked

27%

Avg conflicts / tx

0.39

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,571,031  ·  18 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

8 touches
6 conflicts

0x05958134…6f08

0x065c9d…c394

6 touches
3 conflicts

0x02781be6…2984

0x065c9d…c394

5 touches
3 conflicts

0x338a5e4f…2c4a

0x065c9d…c394

4 touches
1 conflict

0x6ab5f622…5ce9

0x065c9d…c394

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0xe6ff7b92…788b

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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 0x0000000000…00003d

← previous block·next block →recent activity