Block #72,498,167

← previous blocknext block →recent activity

Analyzing

Block #72,498,167

10 transactions · 8 stateful · 2026-05-05 02:01:03 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,498,167  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x350eb8c8…e998

0x065c9d…c394

3 touches
1 conflict

0xff6d959d…70bd

0x065c9d…c394

3 touches
1 conflict

0x031d16b4…895a

0x34b655…2a6f

2 touches
0 conflicts

0x0520da1d…c88e

0x34b655…2a6f

2 touches
0 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

2 touches
0 conflicts

0x1aa8e8ba…8954

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity