← previous blocknext block →recent activity

Analyzing

Block #73,641,028

18 transactions · 16 stateful · 2026-05-10 08:50:43 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,641,028  ·  18 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

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0xb81d3ee7…3947

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x99d5ffa1…4059

0x34b655…2a6f

4 touches
1 conflict

0xad0fa15c…e45b

0x34b655…2a6f

4 touches
1 conflict

0xd49762c9…1359

0x34b655…2a6f

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: 0x065c9d28…a9c394

6 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity