Block #72,309,995

← previous blocknext block →recent activity

Analyzing

Block #72,309,995

12 transactions · 11 stateful · 2026-05-04 05:07:34 UTC

Parallelism

50/100

Blocked

45%

Avg conflicts / tx

1.08

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,309,995  ·  12 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xcf3283ba…c9fa

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x88a7f519…def5

0x065c9d…c394

4 touches
1 conflict

0x0ce7b8ff…ffde

0x065c9d…c394

3 touches
1 conflict

0xf9997a31…50d5

0x065c9d…c394

3 touches
1 conflict

0x5f6f67d1…2810

0x065c9d…c394

3 touches
1 conflict

0xbabb02a4…8394

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

6 conflicts on slot 0xcf3283bab2…c3c9fa

← previous block·next block →recent activity