← previous blocknext block →recent activity

Analyzing

Block #72,977,364

25 transactions · 23 stateful · 2026-05-07 07:13:52 UTC

Parallelism

60/100

Blocked

61%

Avg conflicts / tx

1.12

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #72,977,364  ·  25 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x8bcdc04b…8580

0xd32edf…ff58

9 touches
10 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xcb45d9d6…cb86

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 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: 0xd32edf66…9fff58

10 conflicts on slot 0x8bcdc04b6a…028580

← previous block·next block →recent activity