Block #72,571,245

← previous blocknext block →recent activity

Analyzing

Block #72,571,245

28 transactions · 26 stateful · 2026-05-05 10:07:36 UTC

Parallelism

82/100

Blocked

42%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,571,245  ·  28 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

0x8ab30b2a…cf15

0xd32edf…ff58

7 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

6 touches
3 conflicts

0xcb45d9d6…cb86

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity