← previous blocknext block →recent activity

Analyzing

Block #73,497,252

10 transactions · 9 stateful · 2026-05-09 16:53:04 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,497,252  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0033

0x0ac7c3…d447

2 touches
0 conflicts

0x00000000…0038

0x0ac7c3…d447

2 touches
0 conflicts

0x0ef9fe8a…f2a9

0x0ac7c3…d447

2 touches
0 conflicts

0x14eb477b…87e1

0x0ac7c3…d447

2 touches
0 conflicts

0x15054d5c…d16f

0x0ac7c3…d447

2 touches
0 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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity