← previous blocknext block →recent activity

Analyzing

Block #73,353,435

14 transactions · 13 stateful · 2026-05-09 00:56:11 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,353,435  ·  14 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

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x119e4dea…5e89

0x065c9d…c394

4 touches
1 conflict

0xd821ae10…fe17

0xc8689a…ee79

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9a2b7e95…1e7e

0x065c9d…c394

4 touches
1 conflict

0x9ba13b18…1ded

0x065c9d…c394

4 touches
1 conflict

0xb58e1ef2…8497

0x065c9d…c394

4 touches
1 conflict

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