Block #73,333,862

← previous blocknext block →recent activity

Analyzing

Block #73,333,862

10 transactions · 10 stateful · 2026-05-08 22:45:54 UTC

Parallelism

40/100

Blocked

60%

Avg conflicts / tx

1.3

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,333,862  ·  10 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

0xbdff944d…447e

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x4bc20717…a382

0xd32edf…ff58

5 touches
3 conflicts

0x5d350e8b…3899

0x065c9d…c394

5 touches
3 conflicts

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

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

10 conflicts on slot 0xbdff944d20…a2447e

← previous block·next block →recent activity