Block #73,473,724

← previous blocknext block →recent activity

Analyzing

Block #73,473,724

11 transactions · 9 stateful · 2026-05-09 14:16:30 UTC

Parallelism

55/100

Blocked

44%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,473,724  ·  11 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

6 touches
3 conflicts

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x487faf81…5fa3

0x065c9d…c394

2 touches
0 conflicts

0x51750603…1f93

0x065c9d…c394

2 touches
0 conflicts

0x83180f0a…3a4b

0x065c9d…c394

2 touches
0 conflicts

0xa161e010…0440

0x065c9d…c394

2 touches
0 conflicts

0xc7e2e76c…8e70

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