Block #72,283,937

← previous blocknext block →recent activity

Analyzing

Block #72,283,937

10 transactions · 9 stateful · 2026-05-04 02:13:16 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,283,937  ·  10 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

0xaf40174d…0b3b

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x317e5d20…01f4

0x065c9d…c394

3 touches
1 conflict

0xf104b088…bfdc

0x065c9d…c394

3 touches
1 conflict

0xc69dbb17…5b79

0x065c9d…c394

2 touches
0 conflicts

0xdefadca2…5f30

0x065c9d…c394

2 touches
0 conflicts

0x438cf5f6…f077

0x2a68ba…90c5

2 touches
0 conflicts

0x26d6f1c8…c2b9

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

1 conflict on slot 0xaf40174dcd…f40b3b

← previous block·next block →recent activity