Block #73,187,654

← previous blocknext block →recent activity

Analyzing

Block #73,187,654

10 transactions · 8 stateful · 2026-05-08 06:33:12 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,187,654  ·  10 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

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8e66da19…66b6

0x065c9d…c394

4 touches
1 conflict

0x056dea2d…7f53

0xd32edf…ff58

3 touches
1 conflict

0x4f59ff76…2a4b

0x065c9d…c394

2 touches
0 conflicts

0x8d4fb030…6adb

0x065c9d…c394

2 touches
0 conflicts

0xa78781f8…6e77

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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