← previous blocknext block →recent activity

Analyzing

Block #73,200,922

24 transactions · 15 stateful · 2026-05-08 08:01:30 UTC

Parallelism

75/100

Blocked

53%

Avg conflicts / tx

0.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,200,922  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0x251861eb…78fd

0x34b655…2a6f

6 touches
3 conflicts

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

0xe09eda07…8dda

0x2a68ba…90c5

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…000b

0x6ca43f…c331

4 touches
1 conflict

0x0175b7a6…1db9

0x6ca43f…c331

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