Block #72,314,877

← previous blocknext block →recent activity

Analyzing

Block #72,314,877

8 transactions · 6 stateful · 2026-05-04 05:40:03 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,314,877  ·  8 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5da92df7…74b5

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x9316701f…0d03

0x065c9d…c394

2 touches
0 conflicts

0xb255aa5f…f4a6

0x065c9d…c394

2 touches
0 conflicts

0xb5867a65…deb2

0x065c9d…c394

2 touches
0 conflicts

0xd0668944…4ce1

0x065c9d…c394

2 touches
0 conflicts

0x109d8a52…a7b7

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity