← previous blocknext block →recent activity

Analyzing

Block #72,500,693

9 transactions · 7 stateful · 2026-05-05 02:17:51 UTC

Parallelism

67/100

Blocked

43%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,500,693  ·  9 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

0xdb9d90c4…7ded

0x065c9d…c394

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x7b8a46eb…a3c4

0x065c9d…c394

3 touches
1 conflict

0x04c00b0b…d324

0x065c9d…c394

3 touches
1 conflict

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 0xdb9d90c4b5…bb7ded

← previous block·next block →recent activity