← previous blocknext block →recent activity

Analyzing

Block #72,394,625

35 transactions · 28 stateful · 2026-05-04 14:31:23 UTC

Parallelism

54/100

Blocked

71%

Avg conflicts / tx

2.43

Longest chain

16 deep

Execution timeline

did this block parallelize well?

view

block #72,394,625  ·  35 txs across 16 waves  ·  depth 16
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

wave w13

wave w14

wave w15

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

0xde3907cf…acf2

0xd32edf…ff58

21 touches
55 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001a

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…002a

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

55 conflicts on slot 0xde3907cf6b…7dacf2

← previous block·next block →recent activity