← previous blocknext block →recent activity

Analyzing

Block #72,572,343

16 transactions · 14 stateful · 2026-05-05 10:14:55 UTC

Parallelism

63/100

Blocked

50%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,572,343  ·  16 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb99128bf…6b7b

0x065c9d…c394

7 touches
6 conflicts

0xbd677c44…d42e

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002e

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 0xb99128bf90…166b7b

← previous block·next block →recent activity