← previous blocknext block →recent activity

Analyzing

Block #73,463,919

12 transactions · 11 stateful · 2026-05-09 13:11:16 UTC

Parallelism

58/100

Blocked

36%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,463,919  ·  12 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x1ac914d1…e193

0x065c9d…c394

4 touches
1 conflict

0xc8cabf9b…2745

0x065c9d…c394

3 touches
1 conflict

0xb7bff595…2555

0x065c9d…c394

3 touches
1 conflict

0xbb09b774…79db

0x065c9d…c394

3 touches
1 conflict

0x1a3f6362…85df

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

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity