← previous blocknext block →recent activity

Analyzing

Block #72,973,049

23 transactions · 19 stateful · 2026-05-07 06:45:06 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,973,049  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf4730a2d…3538

0x34b655…2a6f

10 touches
10 conflicts

0x085df2c1…305a

0x34b655…2a6f

6 touches
3 conflicts

0x0eac6378…36f4

0x34b655…2a6f

6 touches
3 conflicts

0x150af51d…9c42

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x3c35979a…975d

0x34b655…2a6f

6 touches
3 conflicts

0x3e6fd7cb…94a6

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: Perpl

10 conflicts on slot 0xf4730a2de3…ef3538

← previous block·next block →recent activity