← previous blocknext block →recent activity

Analyzing

Block #73,263,459

31 transactions · 21 stateful · 2026-05-08 14:57:22 UTC

Parallelism

84/100

Blocked

43%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,263,459  ·  31 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

0xeffb0530…22cd

0xd32edf…ff58

9 touches
10 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdaca243a…f9de

0x34b655…2a6f

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x8d0dfe2c…3345

0x2a68ba…90c5

4 touches
1 conflict

0xb18e2e87…2fdb

0x065c9d…c394

3 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

10 conflicts on slot 0xeffb0530c5…aa22cd

← previous block·next block →recent activity