← previous blocknext block →recent activity

Analyzing

Block #73,035,559

33 transactions · 19 stateful · 2026-05-07 13:41:11 UTC

Parallelism

85/100

Blocked

53%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,035,559  ·  33 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x7882233d…9ab7

0xd32edf…ff58

7 touches
6 conflicts

0x0a85a226…83c1

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xdaca243a…f9de

0x34b655…2a6f

6 touches
3 conflicts

0x0175b7a6…1db9

0x6ca43f…c331

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: 0xd32edf66…9fff58

6 conflicts on slot 0x7882233d87…d89ab7

← previous block·next block →recent activity