← previous blocknext block →recent activity

Analyzing

Block #73,923,949

7 transactions · 7 stateful · 2026-05-11 16:29:14 UTC

Parallelism

57/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,923,949  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x8604446e…0ddc

0x065c9d…c394

3 touches
1 conflict

0x00000000…0001

0x0aa9bd…5d57

2 touches
0 conflicts

0x00000000…0002

0x0aa9bd…5d57

2 touches
0 conflicts

0x00000000…0004

0x0aa9bd…5d57

2 touches
0 conflicts

0x00000000…000c

0x0aa9bd…5d57

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

2 touches
0 conflicts

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

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity