Block #73,651,000

← previous blocknext block →recent activity

Analyzing

Block #73,651,000

15 transactions · 13 stateful · 2026-05-10 09:57:54 UTC

Parallelism

60/100

Blocked

46%

Avg conflicts / tx

1.07

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,651,000  ·  15 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x7f81fb82…633e

0x065c9d…c394

4 touches
1 conflict

0x369cde5a…0517

0xd32edf…ff58

3 touches
1 conflict

0x8aa24fd1…2aa5

0x34b655…2a6f

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

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 0x0000000000…00003d

← previous block·next block →recent activity