← previous blocknext block →recent activity

Analyzing

Block #73,176,518

10 transactions · 8 stateful · 2026-05-08 05:18:55 UTC

Parallelism

60/100

Blocked

38%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,176,518  ·  10 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

0xd3f5f0e0…2683

0x065c9d…c394

4 touches
1 conflict

0xce57a966…d29c

0x065c9d…c394

4 touches
1 conflict

0xf72ef0b2…f1e4

0x065c9d…c394

4 touches
1 conflict

0xfb5ae8f3…2221

0x065c9d…c394

3 touches
1 conflict

0x1629876d…17f2

0x065c9d…c394

3 touches
1 conflict

0xeb90d298…eba1

0x065c9d…c394

3 touches
1 conflict

0x24c0a1df…1d02

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