← previous blocknext block →recent activity

Analyzing

Block #73,598,628

27 transactions · 19 stateful · 2026-05-10 04:06:49 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,598,628  ·  27 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

0x5745f742…13eb

0xd32edf…ff58

9 touches
10 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

8 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x6b115152…2a73

0x34b655…2a6f

6 touches
3 conflicts

0x0a6cb118…4ca5

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

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

10 conflicts on slot 0x5745f7427f…0913eb

← previous block·next block →recent activity