← previous blocknext block →recent activity

Analyzing

Block #72,296,660

28 transactions · 20 stateful · 2026-05-04 03:38:42 UTC

Parallelism

61/100

Blocked

60%

Avg conflicts / tx

2.07

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #72,296,660  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x34aedd33…56c5

0xd32edf…ff58

21 touches
55 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21bf

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x9afb0146…fe65

0x065c9d…c394

5 touches
3 conflicts

0x2906176a…85b6

0x34b655…2a6f

4 touches
1 conflict

0x388f889f…a655

0x34b655…2a6f

4 touches
1 conflict

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

55 conflicts on slot 0x34aedd33e6…bf56c5

← previous block·next block →recent activity