← previous blocknext block →recent activity

Analyzing

Block #72,498,684

17 transactions · 16 stateful · 2026-05-05 02:04:30 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,498,684  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x2484cc15…5afc

0x34b655…2a6f

8 touches
6 conflicts

0x00f245ce…1e10

0x34b655…2a6f

8 touches
6 conflicts

0x893cd52c…5766

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xb2d64c96…d113

0x34b655…2a6f

8 touches
6 conflicts

0xe1fd24a0…eaa6

0x34b655…2a6f

8 touches
6 conflicts

0xffedaa84…311b

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity