Block #73,596,318

← previous blocknext block →recent activity

Analyzing

Block #73,596,318

23 transactions · 21 stateful · 2026-05-10 03:51:30 UTC

Parallelism

70/100

Blocked

67%

Avg conflicts / tx

1.43

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,596,318  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x22e295f5…1bef

0x065c9d…c394

12 touches
15 conflicts

0x4d87512b…897c

0x065c9d…c394

10 touches
10 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xaae36ada…f073

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

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: 0x065c9d28…a9c394

15 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity