← previous blocknext block →recent activity

Analyzing

Block #73,029,476

31 transactions · 26 stateful · 2026-05-07 13:00:41 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.68

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,029,476  ·  31 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x0b390c61…dc07

0x065c9d…c394

8 touches
6 conflicts

0x60b0ea38…99e4

0xd32edf…ff58

7 touches
6 conflicts

0x479ce48c…fa1a

0x1b6862…e19c

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xb389d45f…8a4c

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

4 touches
1 conflict

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0b390c6160…02dc07

← previous block·next block →recent activity