← previous blocknext block →recent activity

Analyzing

Block #72,282,996

30 transactions · 24 stateful · 2026-05-04 02:06:55 UTC

Parallelism

70/100

Blocked

58%

Avg conflicts / tx

1.7

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,282,996  ·  30 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x1996388a…75ff

0xd32edf…ff58

15 touches
28 conflicts

0x17606ba6…1b6e

0x754704…b603

14 touches
21 conflicts

0xebde29d9…5739

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

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: 0xd32edf66…9fff58

28 conflicts on slot 0x1996388a00…8a75ff

← previous block·next block →recent activity