← previous blocknext block →recent activity

Analyzing

Block #73,681,358

8 transactions · 8 stateful · 2026-05-10 13:22:50 UTC

Parallelism

63/100

Blocked

38%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,681,358  ·  8 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

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x3e733ae4…4598

0x34b655…2a6f

4 touches
1 conflict

0x6e0ce9d7…bce9

0x065c9d…c394

3 touches
1 conflict

0x0ff6287f…0304

0x065c9d…c394

2 touches
0 conflicts

0x39889e54…ad49

0x065c9d…c394

2 touches
0 conflicts

0x3f80a230…c48e

0x065c9d…c394

2 touches
0 conflicts

0x4a15ff0f…4abf

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

1 conflict on slot 0x0ac3194537…8f2c72

← previous block·next block →recent activity