← previous blocknext block →recent activity

Analyzing

Block #73,395,316

14 transactions · 13 stateful · 2026-05-09 05:34:42 UTC

Parallelism

79/100

Blocked

15%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,395,316  ·  14 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

6 touches
3 conflicts

0x541f41c1…0d94

0x065c9d…c394

4 touches
1 conflict

0x41cfa9e2…eec8

0x065c9d…c394

3 touches
1 conflict

0x3f2beb9d…2303

0x065c9d…c394

3 touches
1 conflict

0x1c90f748…9418

0x065c9d…c394

2 touches
0 conflicts

0x2f9624d5…ce01

0x065c9d…c394

2 touches
0 conflicts

0x489b4586…883d

0x065c9d…c394

2 touches
0 conflicts

0x8b63bcaa…d2f3

0x065c9d…c394

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity