Block #72,370,999

← previous blocknext block →recent activity

Analyzing

Block #72,370,999

22 transactions · 19 stateful · 2026-05-04 11:53:52 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,370,999  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x4d4a04ca…84a0

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity