← previous blocknext block →recent activity

Analyzing

Block #73,693,761

18 transactions · 16 stateful · 2026-05-10 14:46:23 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,693,761  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0ac31945…2c72

0x065c9d…c394

8 touches
6 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x3a3097d7…2ab6

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

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 0x0ac3194537…8f2c72

← previous block·next block →recent activity