Block #72,167,108

← previous blocknext block →recent activity

Analyzing

Block #72,167,108

10 transactions · 10 stateful · 2026-05-03 13:08:14 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

1.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,167,108  ·  10 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xce74be7d…2b3c

0x065c9d…c394

7 touches
6 conflicts

0xc70fef68…baf1

0xd32edf…ff58

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba61

0x188d58…ea8e

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb86

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

10 conflicts on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity