← previous blocknext block →recent activity

Analyzing

Block #73,599,821

21 transactions · 14 stateful · 2026-05-10 04:14:47 UTC

Parallelism

76/100

Blocked

43%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,599,821  ·  21 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x8a35acfb…d1aa

0x8d66a4…3095

6 touches
3 conflicts

0xafd59af5…5257

0xc8689a…ee79

4 touches
1 conflict

0xac808a27…82db

0x34b655…2a6f

4 touches
1 conflict

0xbbad5c01…454e

0x34b655…2a6f

4 touches
1 conflict

0xfea45f33…4a77

0x34b655…2a6f

4 touches
1 conflict

0x7f430e47…4cbd

0x8d66a4…3095

4 touches
1 conflict

0xe72962f6…e169

0x8d66a4…3095

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: 0x34b6552d…112a6f

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity