← previous blocknext block →recent activity

Analyzing

Block #72,817,366

18 transactions · 11 stateful · 2026-05-06 13:28:24 UTC

Parallelism

83/100

Blocked

27%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,817,366  ·  18 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

0xe49bddf8…3f4e

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c2

0x1b6862…e19c

4 touches
1 conflict

0xba3047ea…4069

0x065c9d…c394

3 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

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: 0xd32edf66…9fff58

3 conflicts on slot 0xe49bddf8ce…7f3f4e

← previous block·next block →recent activity