← previous blocknext block →recent activity

Analyzing

Block #72,266,786

13 transactions · 9 stateful · 2026-05-04 00:18:00 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,266,786  ·  13 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

0x10f5f4d8…572e

0x34b655…2a6f

6 touches
3 conflicts

0x280d1119…ee4d

0x34b655…2a6f

6 touches
3 conflicts

0x94710b77…a921

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xbd64801a…6689

0x34b655…2a6f

6 touches
3 conflicts

0xd8d5abde…3a4a

0x34b655…2a6f

6 touches
3 conflicts

0xfcdce647…58ca

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