Block #73,814,599

← previous blocknext block →recent activity

Analyzing

Block #73,814,599

15 transactions · 12 stateful · 2026-05-11 04:20:42 UTC

Parallelism

60/100

Blocked

42%

Avg conflicts / tx

0.93

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,814,599  ·  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

0x22e295f5…1bef

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x4db87dbf…4c4a

0x065c9d…c394

2 touches
0 conflicts

0x664c56c5…d2a6

0x065c9d…c394

2 touches
0 conflicts

0x76c5d5c9…945c

0x065c9d…c394

2 touches
0 conflicts

0xeb7cd91c…31ab

0x065c9d…c394

2 touches
0 conflicts

0xae69c125…2379

0x2a68ba…90c5

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

10 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity