← previous blocknext block →recent activity

Analyzing

Block #72,288,053

32 transactions · 23 stateful · 2026-05-04 02:40:58 UTC

Parallelism

66/100

Blocked

52%

Avg conflicts / tx

1.78

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #72,288,053  ·  32 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

0x1702d6c3…245e

0xd32edf…ff58

21 touches
55 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xdafd154f…8d3b

0x065c9d…c394

3 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

2 touches
0 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

2 touches
0 conflicts

0x207c32d3…d39b

0x34b655…2a6f

2 touches
0 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

2 touches
0 conflicts

0x8a85cf3d…2868

0x34b655…2a6f

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

55 conflicts on slot 0x1702d6c3e5…47245e

← previous block·next block →recent activity