← previous blocknext block →recent activity

Analyzing

Block #73,677,610

10 transactions · 8 stateful · 2026-05-10 12:57:31 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,677,610  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x51b05589…27b7

0x065c9d…c394

4 touches
1 conflict

0x5a6db229…e6c8

0x065c9d…c394

3 touches
1 conflict

0x85491d51…5f2f

0x065c9d…c394

3 touches
1 conflict

0x261d4d02…e160

0x065c9d…c394

2 touches
0 conflicts

0x3e613abe…5a5b

0x065c9d…c394

2 touches
0 conflicts

0x4556d88c…82cf

0x065c9d…c394

2 touches
0 conflicts

0x4bcbe3dc…19d7

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

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity