← previous blocknext block →recent activity

Analyzing

Block #72,283,070

36 transactions · 32 stateful · 2026-05-04 02:07:25 UTC

Parallelism

83/100

Blocked

66%

Avg conflicts / tx

1.31

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,283,070  ·  36 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x25c7e66c…ca67

0xd32edf…ff58

11 touches
15 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x9a555477…19a8

0x754704…b603

8 touches
6 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0000

0x63e48b…53f2

8 touches
6 conflicts

0x00000000…0003

0x63e48b…53f2

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

15 conflicts on slot 0x25c7e66ced…daca67

← previous block·next block →recent activity