← previous blocknext block →recent activity

Analyzing

Block #72,296,029

17 transactions · 12 stateful · 2026-05-04 03:34:30 UTC

Parallelism

71/100

Blocked

33%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,296,029  ·  17 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

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0x0ff280de…991f

0x065c9d…c394

7 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xf3ea7041…aafb

0x065c9d…c394

3 touches
1 conflict

0x4bef88e0…eaca

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0000

0x453805…c7fd

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity