Block #72,171,865

← previous blocknext block →recent activity

Analyzing

Block #72,171,865

8 transactions · 6 stateful · 2026-05-03 13:40:10 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,171,865  ·  8 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

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x63df6af2…71eb

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0eb7e6ff…cd34

0x065c9d…c394

2 touches
0 conflicts

0x138acd03…7774

0x065c9d…c394

2 touches
0 conflicts

0xe95ea48f…9157

0x065c9d…c394

2 touches
0 conflicts

0xec82ec4a…caa5

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

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

1 conflict on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity