← previous blocknext block →recent activity

Analyzing

Block #72,395,267

14 transactions · 11 stateful · 2026-05-04 14:35:39 UTC

Parallelism

64/100

Blocked

36%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,395,267  ·  14 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

8 touches
6 conflicts

0x1a64fc11…76d7

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xe614c509…7990

0xd32edf…ff58

3 touches
1 conflict

0xaa5dbabc…b614

0x065c9d…c394

3 touches
1 conflict

0xc09e8320…7661

0x065c9d…c394

3 touches
1 conflict

0x87c6858e…7f76

0x065c9d…c394

3 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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity