← previous blocknext block →recent activity

Analyzing

Block #72,496,361

9 transactions · 9 stateful · 2026-05-05 01:49:02 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,496,361  ·  9 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

0xcd8ceb90…c134

0x96b79e…d00a

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x02e0c10f…a495

0x065c9d…c394

2 touches
0 conflicts

0x13f2150f…ef62

0x065c9d…c394

2 touches
0 conflicts

0x3cd91bc3…061f

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

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: 0x96b79ef4…d2d00a

1 conflict on slot 0xcd8ceb9090…dac134

← previous block·next block →recent activity