← previous blocknext block →recent activity

Analyzing

Block #73,495,607

16 transactions · 14 stateful · 2026-05-09 16:42:06 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.81

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,495,607  ·  16 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x4b08ba2d…7294

0x065c9d…c394

4 touches
1 conflict

0x821699bb…78a2

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xd4d493aa…eb18

0x065c9d…c394

3 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 0x046a928e85…e50012

← previous block·next block →recent activity