Block #72,496,658

← previous blocknext block →recent activity

Analyzing

Block #72,496,658

15 transactions · 13 stateful · 2026-05-05 01:51:00 UTC

Parallelism

80/100

Blocked

23%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,496,658  ·  15 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x517286ba…e90a

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xa76ef642…2577

0x065c9d…c394

3 touches
1 conflict

0x60b6425e…a3f6

0x065c9d…c394

3 touches
1 conflict

0xbb7625f0…29b5

0x065c9d…c394

2 touches
0 conflicts

0xec83a29d…6f98

0x065c9d…c394

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