Block #72,855,963

← previous blocknext block →recent activity

Analyzing

Block #72,855,963

22 transactions · 19 stateful · 2026-05-06 17:45:53 UTC

Parallelism

64/100

Blocked

63%

Avg conflicts / tx

1.73

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,855,963  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x71034e47…a8d6

0xd32edf…ff58

15 touches
28 conflicts

0x70b2f813…783c

0x2a68ba…90c5

10 touches
10 conflicts

0xba5743c7…21c3

0x1b6862…e19c

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

6 touches
3 conflicts

0xec08a7a5…12f6

0x065c9d…c394

5 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

28 conflicts on slot 0x71034e47c9…bda8d6

← previous block·next block →recent activity