Block #72,225,154

← previous blocknext block →recent activity

Analyzing

Block #72,225,154

8 transactions · 8 stateful · 2026-05-03 19:38:09 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,225,154  ·  8 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

0xa314b0f3…2efe

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8fdcfa5e…0ad4

0x065c9d…c394

3 touches
1 conflict

0xbedd622a…2dab

0x065c9d…c394

3 touches
1 conflict

0x3f2ac0a6…06c1

0x065c9d…c394

2 touches
0 conflicts

0x551ae5c7…7d63

0x065c9d…c394

2 touches
0 conflicts

0x8ccbe183…4ff2

0x065c9d…c394

2 touches
0 conflicts

0xb99b8296…5dd8

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 0xa314b0f38b…fc2efe

← previous block·next block →recent activity