← previous blocknext block →recent activity

Analyzing

Block #72,284,167

11 transactions · 10 stateful · 2026-05-04 02:14:49 UTC

Parallelism

73/100

Blocked

30%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,284,167  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xafd59af5…5257

0xc8689a…ee79

6 touches
3 conflicts

0x2484cc15…5afc

0x34b655…2a6f

6 touches
3 conflicts

0x2a2e1210…90ff

0x34b655…2a6f

6 touches
3 conflicts

0x49339736…b223

0x34b655…2a6f

6 touches
3 conflicts

0x4ad3cbd6…030d

0x34b655…2a6f

6 touches
3 conflicts

0x4f4bdabd…ffba

0x34b655…2a6f

6 touches
3 conflicts

0x5fbee329…f1de

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

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: 0xc8689a47…62ee79

3 conflicts on slot 0xafd59af545…b35257

← previous block·next block →recent activity