Block #73,176,465

← previous blocknext block →recent activity

Analyzing

Block #73,176,465

13 transactions · 11 stateful · 2026-05-08 05:18:34 UTC

Parallelism

46/100

Blocked

55%

Avg conflicts / tx

1.62

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,176,465  ·  13 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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x2a354a63…0515

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xce57a966…d29c

0x065c9d…c394

6 touches
3 conflicts

0xda4702ed…be8b

0x065c9d…c394

5 touches
3 conflicts

0x15861eab…fc45

0x065c9d…c394

4 touches
2 conflicts

0xc7d5096a…5dc8

0x065c9d…c394

4 touches
2 conflicts

0xd584d41d…a5e6

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

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity