← previous blocknext block →recent activity

Analyzing

Block #72,272,291

11 transactions · 10 stateful · 2026-05-04 00:54:58 UTC

Parallelism

64/100

Blocked

40%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,272,291  ·  11 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd8305f48…b574

0xd32edf…ff58

5 touches
3 conflicts

0x280d1119…ee4d

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xb08d4697…98b6

0x065c9d…c394

3 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0xda6b535e…6d67

0x1b6862…e19c

2 touches
0 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

3 conflicts on slot 0xd8305f484b…1eb574

← previous block·next block →recent activity