← previous blocknext block →recent activity

Analyzing

Block #72,284,260

21 transactions · 19 stateful · 2026-05-04 02:15:26 UTC

Parallelism

62/100

Blocked

58%

Avg conflicts / tx

1.52

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,284,260  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

12 touches
15 conflicts

0xbad68552…e6bf

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x35b65947…44d1

0xc8689a…ee79

6 touches
3 conflicts

0x005fb969…2d97

0x34b655…2a6f

6 touches
3 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity