Block #72,855,972

← previous blocknext block →recent activity

Analyzing

Block #72,855,972

25 transactions · 20 stateful · 2026-05-06 17:45:57 UTC

Parallelism

76/100

Blocked

55%

Avg conflicts / tx

0.72

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,855,972  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf4730a2d…3538

0x34b655…2a6f

8 touches
6 conflicts

0xfb36fbbf…844a

0xd32edf…ff58

5 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x0b873f52…4fde

0x34b655…2a6f

4 touches
1 conflict

0x0eac6378…36f4

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: 0x34b6552d…112a6f

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity