Block #72,496,665

← previous blocknext block →recent activity

Analyzing

Block #72,496,665

8 transactions · 6 stateful · 2026-05-05 01:51:03 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,496,665  ·  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

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x7df3a102…6b6b

0x065c9d…c394

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x60c1ef1e…5c2f

0x065c9d…c394

4 touches
1 conflict

0x7df3a102…6b6c

0x065c9d…c394

3 touches
1 conflict

0x5762ff15…2bd5

0x065c9d…c394

3 touches
1 conflict

0x74e71984…ae90

0x2a68ba…90c5

2 touches
0 conflicts

0xbf04f37d…85f2

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

3 conflicts on slot 0xc3c8642ae9…317da5

← previous block·next block →recent activity