← previous blocknext block →recent activity

Analyzing

Block #72,284,067

5 transactions · 4 stateful · 2026-05-04 02:14:07 UTC

Parallelism

60/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,284,067  ·  5 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

0xccd93d4e…1e8e

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbeee63ff…da66

0x065c9d…c394

4 touches
1 conflict

0xcdc6102c…f6e9

0x065c9d…c394

3 touches
1 conflict

0xdd2d7be9…1c0d

0x065c9d…c394

3 touches
1 conflict

0x2821d026…ed6c

0x065c9d…c394

3 touches
1 conflict

0x1a4b4152…0a08

0x8d0464…4402

2 touches
0 conflicts

0x2e2214a9…fe0d

0x8d0464…4402

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 0xccd93d4ec3…9a1e8e

← previous block·next block →recent activity