← previous blocknext block →recent activity

Analyzing

Block #72,856,157

30 transactions · 25 stateful · 2026-05-06 17:47:09 UTC

Parallelism

67/100

Blocked

68%

Avg conflicts / tx

1.63

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #72,856,157  ·  30 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

0xd23676f4…0a2e

0xd32edf…ff58

13 touches
21 conflicts

0x7f189cf6…afab

0x065c9d…c394

8 touches
6 conflicts

0x388e001a…7e04

0x34b655…2a6f

8 touches
6 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

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

21 conflicts on slot 0xd23676f4d2…9f0a2e

← previous block·next block →recent activity