Block #73,970,875

← previous blocknext block →recent activity

Analyzing

Block #73,970,875

13 transactions · 11 stateful · 2026-05-11 21:41:26 UTC

Parallelism

62/100

Blocked

36%

Avg conflicts / tx

0.38

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,970,875  ·  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

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x88ff6862…a556

0x065c9d…c394

3 touches
1 conflict

0xb1e0051c…fc12

0xd32edf…ff58

3 touches
1 conflict

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x00000000…0015

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

1 conflict on slot 0x6f08361da9…89bda6

← previous block·next block →recent activity