← previous blocknext block →recent activity

Analyzing

Block #72,571,573

8 transactions · 7 stateful · 2026-05-05 10:09:47 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,571,573  ·  8 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xcf9df718…9daa

0x065c9d…c394

4 touches
1 conflict

0x43ec339a…7688

0x065c9d…c394

4 touches
1 conflict

0xa4725660…6ee3

0x065c9d…c394

4 touches
1 conflict

0xb45641cd…907b

0x065c9d…c394

3 touches
1 conflict

0x9d72aed3…ce75

0x065c9d…c394

3 touches
1 conflict

0xdfe4f6db…159a

0x065c9d…c394

3 touches
1 conflict

0x0a640f6a…1353

0x065c9d…c394

3 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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity