← previous blocknext block →recent activity

Analyzing

Block #72,497,024

7 transactions · 6 stateful · 2026-05-05 01:53:26 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,497,024  ·  7 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

0x74e71984…ae90

0x2a68ba…90c5

4 touches
1 conflict

0x2a70a1a1…a328

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xce768f9c…8beb

0x065c9d…c394

3 touches
1 conflict

0x4ecbf04d…458a

0x065c9d…c394

3 touches
1 conflict

0x25276f8d…4fd7

0x065c9d…c394

3 touches
1 conflict

0x72e9a6f4…75f3

0x065c9d…c394

3 touches
1 conflict

0x4dd1db39…a996

0x188d58…ea8e

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 0x74e71984e8…06ae90

← previous block·next block →recent activity