Block #72,296,324

← previous blocknext block →recent activity

Analyzing

Block #72,296,324

16 transactions · 15 stateful · 2026-05-04 03:36:28 UTC

Parallelism

69/100

Blocked

47%

Avg conflicts / tx

1.06

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,296,324  ·  16 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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0xbbee74c2…567a

0x065c9d…c394

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x6e290d7e…93d7

0x34b655…2a6f

4 touches
1 conflict

0x75f928fc…0465

0x34b655…2a6f

4 touches
1 conflict

0x7cee1be1…e770

0x34b655…2a6f

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

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity