← previous blocknext block →recent activity

Analyzing

Block #73,647,635

28 transactions · 21 stateful · 2026-05-10 09:35:16 UTC

Parallelism

75/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,647,635  ·  28 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

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x6b1259e6…4e10

0x1b6862…e19c

8 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xdbc5ce04…7a41

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001b

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: 0x1b68626d…2de19c

6 conflicts on slot 0x0000000000…000013

← previous block·next block →recent activity