Block #73,176,352

← previous blocknext block →recent activity

Analyzing

Block #73,176,352

13 transactions · 11 stateful · 2026-05-08 05:17:49 UTC

Parallelism

77/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,176,352  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x2a354a63…0515

0x065c9d…c394

2 touches
0 conflicts

0x3f7f7584…1934

0x065c9d…c394

2 touches
0 conflicts

0x4b19145c…5900

0x065c9d…c394

2 touches
0 conflicts

0x72487851…da8b

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity