← previous blocknext block →recent activity

Analyzing

Block #72,498,702

37 transactions · 30 stateful · 2026-05-05 02:04:37 UTC

Parallelism

78/100

Blocked

67%

Avg conflicts / tx

1.35

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,498,702  ·  37 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

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xffe431af…8faa

0x065c9d…c394

10 touches
10 conflicts

0x4074553f…61f3

0xd32edf…ff58

9 touches
10 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x3a3097d7…2ab6

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

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: 0x754704bc…afb603

10 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity