Block #72,094,766

← previous blocknext block →recent activity

Analyzing

Block #72,094,766

13 transactions · 12 stateful · 2026-05-03 05:06:37 UTC

Parallelism

62/100

Blocked

33%

Avg conflicts / tx

0.92

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,094,766  ·  13 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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0xbbee74c2…567a

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001c

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002c

0x1b6862…e19c

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 0xf2f76ab392…f3623e

← previous block·next block →recent activity