← previous blocknext block →recent activity

Analyzing

Block #72,233,813

38 transactions · 32 stateful · 2026-05-03 20:36:23 UTC

Parallelism

71/100

Blocked

66%

Avg conflicts / tx

1.66

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #72,233,813  ·  38 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x2ed00f98…da9f

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…0002

0x7e9d3a…9fda

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x50c2960c…5f37

0x34b655…2a6f

8 touches
6 conflicts

0xafd59af5…5257

0xc8689a…ee79

8 touches
6 conflicts

0x00f245ce…1e10

0x34b655…2a6f

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: 0x34b6552d…112a6f

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity