← previous blocknext block →recent activity

Analyzing

Block #72,286,173

27 transactions · 25 stateful · 2026-05-04 02:28:19 UTC

Parallelism

81/100

Blocked

48%

Avg conflicts / tx

0.96

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,286,173  ·  27 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

0xd39676e8…c273

0xd32edf…ff58

7 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x9a555477…19a8

0x754704…b603

6 touches
3 conflicts

0x00000000…0000

0xd5b70d…615b

6 touches
3 conflicts

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0004

0xd5b70d…615b

6 touches
3 conflicts

0x7c403af1…31b1

0x3bd359…433a

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 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

6 conflicts on slot 0xd39676e837…b4c273

← previous block·next block →recent activity