Block #72,859,950

← previous blocknext block →recent activity

Analyzing

Block #72,859,950

44 transactions · 32 stateful · 2026-05-06 18:12:23 UTC

Parallelism

70/100

Blocked

72%

Avg conflicts / tx

1.57

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #72,859,950  ·  44 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0xdcddff15…325d

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

12 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

12 touches
15 conflicts

0x10c19272…7443

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…002c

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001c

0x1b6862…e19c

10 touches
10 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 0xdcddff154a…ff325d

← previous block·next block →recent activity