← previous blocknext block →recent activity

Analyzing

Block #72,429,067

25 transactions · 20 stateful · 2026-05-04 18:20:52 UTC

Parallelism

44/100

Blocked

75%

Avg conflicts / tx

3.76

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #72,429,067  ·  25 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

0xa27767d1…ff1a

0xd32edf…ff58

27 touches
91 conflicts

0x00000000…0004

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0002

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x9a555477…19a8

0x754704…b603

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x6c6f37ba…c208

0x1b6862…e19c

4 touches
1 conflict

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

91 conflicts on slot 0xa27767d12c…5cff1a

← previous block·next block →recent activity