← previous blocknext block →recent activity

Analyzing

Block #73,034,137

20 transactions · 20 stateful · 2026-05-07 13:31:45 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

1.8

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,034,137  ·  20 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

0xfe4f2499…7e67

0xd32edf…ff58

15 touches
28 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x3a3097d7…2ab9

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

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

28 conflicts on slot 0xfe4f249936…2a7e67

← previous block·next block →recent activity