Block #73,334,432

← previous blocknext block →recent activity

Analyzing

Block #73,334,432

13 transactions · 10 stateful · 2026-05-08 22:49:41 UTC

Parallelism

62/100

Blocked

40%

Avg conflicts / tx

0.69

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,334,432  ·  13 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

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0xdbc6e634…e16a

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xd112013a…c581

0xd32edf…ff58

3 touches
1 conflict

0x0d76ab4c…6ef3

0x065c9d…c394

2 touches
0 conflicts

0x91d9ca87…a644

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