Block #72,286,098

← previous blocknext block →recent activity

Analyzing

Block #72,286,098

8 transactions · 7 stateful · 2026-05-04 02:27:49 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,286,098  ·  8 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xcdb9ffb4…41c0

0x065c9d…c394

4 touches
1 conflict

0xd4e962f8…5d60

0x065c9d…c394

4 touches
1 conflict

0xe991de75…cfbc

0x065c9d…c394

3 touches
1 conflict

0xfe3819a5…e3c1

0x065c9d…c394

3 touches
1 conflict

0xaa93081a…560c

0x065c9d…c394

2 touches
0 conflicts

0xbbee74c2…567a

0x065c9d…c394

2 touches
0 conflicts

0x74e71984…ae90

0x2a68ba…90c5

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity