← previous blocknext block →recent activity

Analyzing

Block #73,599,749

8 transactions · 8 stateful · 2026-05-10 04:14:19 UTC

Parallelism

50/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,599,749  ·  8 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x683304b2…c42f

0x065c9d…c394

4 touches
1 conflict

0xd49d7936…21ed

0x065c9d…c394

3 touches
1 conflict

0xabbce276…6966

0x065c9d…c394

3 touches
1 conflict

0x236b65e3…294d

0x065c9d…c394

2 touches
0 conflicts

0x3cb299b7…a7e2

0x065c9d…c394

2 touches
0 conflicts

0x803ba8bc…0c5d

0x065c9d…c394

2 touches
0 conflicts

0x9d62dcfd…54a7

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