Block #73,501,289

← previous blocknext block →recent activity

Analyzing

Block #73,501,289

13 transactions · 12 stateful · 2026-05-09 17:19:58 UTC

Parallelism

54/100

Blocked

50%

Avg conflicts / tx

1.23

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,501,289  ·  13 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x1c3d4f13…9f90

0x065c9d…c394

2 touches
0 conflicts

0x2fb60836…1e5b

0x065c9d…c394

2 touches
0 conflicts

0x36373720…343d

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

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity