Block #72,371,096

← previous blocknext block →recent activity

Analyzing

Block #72,371,096

7 transactions · 6 stateful · 2026-05-04 11:54:31 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,371,096  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x45855fc6…68f6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5fb4a9e1…0c92

0x065c9d…c394

4 touches
1 conflict

0xf26da4e2…2bfa

0x065c9d…c394

3 touches
1 conflict

0xf955e3ef…5ead

0x065c9d…c394

3 touches
1 conflict

0x1441f298…4727

0x065c9d…c394

3 touches
1 conflict

0x6bd6a013…78f6

0x065c9d…c394

2 touches
0 conflicts

0xb177968a…389b

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 0x45855fc614…7868f6

← previous block·next block →recent activity