← previous blocknext block →recent activity

Analyzing

Block #72,309,618

7 transactions · 6 stateful · 2026-05-04 05:05:03 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,309,618  ·  7 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

0x55042839…fc22

0x065c9d…c394

4 touches
1 conflict

0x69a69b68…7b5a

0x065c9d…c394

3 touches
1 conflict

0x99d8345d…8d90

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x07d330fc…bb55

0x065c9d…c394

2 touches
0 conflicts

0x1bbf996a…7ed3

0x065c9d…c394

2 touches
0 conflicts

0x66d95297…f93f

0x065c9d…c394

2 touches
0 conflicts

0xf2f76ab3…623e

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

1 conflict on slot 0x5504283926…18fc22

← previous block·next block →recent activity