← previous blocknext block →recent activity

Analyzing

Block #72,309,588

7 transactions · 6 stateful · 2026-05-04 05:04:51 UTC

Parallelism

71/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,309,588  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x544ac270…ab6b

0x3bd359…433a

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x5d3cd371…684a

0x065c9d…c394

2 touches
0 conflicts

0x6dbd4f54…fb26

0x065c9d…c394

2 touches
0 conflicts

0x88d8d37a…ffcb

0x065c9d…c394

2 touches
0 conflicts

0xc73a42c1…6282

0x065c9d…c394

2 touches
0 conflicts

0xcf3283ba…c9fa

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity