← previous blocknext block →recent activity

Analyzing

Block #72,288,016

10 transactions · 7 stateful · 2026-05-04 02:40:43 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,288,016  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x7d54cee3…7402

0x065c9d…c394

4 touches
1 conflict

0x438cf5f6…f077

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x25e7ceef…c51d

0xd32edf…ff58

3 touches
1 conflict

0xa980598e…ec52

0x3bd359…433a

2 touches
0 conflicts

0xfe3bddd2…8b48

0x3bd359…433a

2 touches
0 conflicts

0x1e349dde…a33a

0x754704…b603

2 touches
0 conflicts

0x01a89030…f786

0x98dc6e…8633

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 0x7d54cee3f4…817402

← previous block·next block →recent activity