Block #72,099,584

← previous blocknext block →recent activity

Analyzing

Block #72,099,584

10 transactions · 8 stateful · 2026-05-03 05:38:40 UTC

Parallelism

70/100

Blocked

25%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,099,584  ·  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

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xd025d7d7…f05a

0x3bd359…433a

4 touches
1 conflict

0x60b24061…7c24

0x188d58…ea8e

2 touches
0 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

2 touches
0 conflicts

0xe75ce681…ba61

0x188d58…ea8e

2 touches
0 conflicts

0x05a30e31…2713

0x3bd359…433a

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: 0x188d586d…f9ea8e

1 conflict on slot 0x01e7b86585…4d6e6d

← previous block·next block →recent activity