Block #73,664,029

← previous blocknext block →recent activity

Analyzing

Block #73,664,029

21 transactions · 20 stateful · 2026-05-10 11:25:41 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

1.52

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,664,029  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xb159af88…a9e7

0x065c9d…c394

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x7f81fb82…633e

0x065c9d…c394

8 touches
6 conflicts

0x2f889c82…a645

0xd32edf…ff58

3 touches
1 conflict

0xfe3bddd2…8b48

0x3bd359…433a

2 touches
0 conflicts

0x4e368b2b…09ac

0x754704…b603

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

15 conflicts on slot 0xb159af880b…47a9e7

← previous block·next block →recent activity