Block #72,228,436

← previous blocknext block →recent activity

Analyzing

Block #72,228,436

10 transactions · 8 stateful · 2026-05-03 20:00:14 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,228,436  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x66f64d38…bbe2

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0xeda2edc3…91d8

0x000000…012a

2 touches
0 conflicts

0xf7c60661…f490

0x065c9d…c394

2 touches
0 conflicts

0x33018431…8f5c

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: 0xd32edf66…9fff58

3 conflicts on slot 0x66f64d38ab…51bbe2

← previous block·next block →recent activity