← previous blocknext block →recent activity

Analyzing

Block #73,043,071

34 transactions · 24 stateful · 2026-05-07 14:31:12 UTC

Parallelism

71/100

Blocked

63%

Avg conflicts / tx

1.44

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,043,071  ·  34 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

0x8b0108c8…0c25

0xd32edf…ff58

15 touches
28 conflicts

0xf91b744e…9117

0x754704…b603

10 touches
10 conflicts

0xce8bbe33…b72e

0x3bd359…433a

10 touches
10 conflicts

0x6af306bb…2e81

0x3bd359…433a

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001f

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

8 touches
6 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 0x8b0108c8d6…8d0c25

← previous block·next block →recent activity