Block #72,301,285

← previous blocknext block →recent activity

Analyzing

Block #72,301,285

11 transactions · 9 stateful · 2026-05-04 04:09:31 UTC

Parallelism

45/100

Blocked

67%

Avg conflicts / tx

1.55

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,301,285  ·  11 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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0x6babf30d…e57e

0x065c9d…c394

4 touches
1 conflict

0x12535e11…b23c

0x065c9d…c394

4 touches
1 conflict

0x8caca8b2…a7bf

0x065c9d…c394

4 touches
1 conflict

0xe6719563…142b

0x065c9d…c394

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity