← previous blocknext block →recent activity

Analyzing

Block #72,296,693

9 transactions · 8 stateful · 2026-05-04 03:38:56 UTC

Parallelism

56/100

Blocked

38%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,296,693  ·  9 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0xb0e505e9…6605

0x065c9d…c394

7 touches
6 conflicts

0xba5743c7…21bf

0x1b6862…e19c

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xfc0c62af…2279

0xd32edf…ff58

3 touches
1 conflict

0x8c6f8e19…63b9

0x754704…b603

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity