← previous blocknext block →recent activity

Analyzing

Block #73,202,728

12 transactions · 10 stateful · 2026-05-08 08:13:30 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,202,728  ·  12 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x7f189cf6…afab

0x065c9d…c394

4 touches
1 conflict

0x2783a539…c538

0x065c9d…c394

4 touches
1 conflict

0x3b8ffd61…f3ad

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0fa3de7d…feb4

0x34b655…2a6f

4 touches
1 conflict

0xbac876a6…d4c2

0x065c9d…c394

3 touches
1 conflict

0x6db33d2e…dffd

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity