← previous blocknext block →recent activity

Analyzing

Block #72,300,887

7 transactions · 6 stateful · 2026-05-04 04:06:52 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,300,887  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x70a7e957…98bd

0x065c9d…c394

4 touches
1 conflict

0xab7306cb…c604

0x065c9d…c394

3 touches
1 conflict

0xba1825bb…e754

0x065c9d…c394

3 touches
1 conflict

0xcb2050c1…0b84

0x065c9d…c394

3 touches
1 conflict

0x00000000…0005

0x0594c7…a3be

2 touches
0 conflicts

0x5c83af9a…a685

0x0594c7…a3be

2 touches
0 conflicts

0x5f9e9857…8ad6

0x0594c7…a3be

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 0x0000000000…00003d

← previous block·next block →recent activity