Block #73,211,846

← previous blocknext block →recent activity

Analyzing

Block #73,211,846

10 transactions · 9 stateful · 2026-05-08 09:14:08 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,211,846  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5603f54d…7ab9

0x065c9d…c394

2 touches
0 conflicts

0xa0b37a77…304c

0x065c9d…c394

2 touches
0 conflicts

0xc9e7bdbe…9f0b

0x065c9d…c394

2 touches
0 conflicts

0xcdaafc9e…0fca

0x065c9d…c394

2 touches
0 conflicts

0x490911cc…5fea

0x0c65a0…0852

2 touches
0 conflicts

0xe1a9f4db…2590

0x0c65a0…0852

2 touches
0 conflicts

0x70b2f813…783c

0x2a68ba…90c5

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity