Block #73,261,375

← previous blocknext block →recent activity

Analyzing

Block #73,261,375

17 transactions · 17 stateful · 2026-05-08 14:43:30 UTC

Parallelism

47/100

Blocked

65%

Avg conflicts / tx

2.24

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,261,375  ·  17 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xf2f76ab3…623e

0x2a68ba…90c5

14 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0x35ca9d96…6c96

0x065c9d…c394

3 touches
1 conflict

0x5a1cd68f…4125

0x754704…b603

2 touches
0 conflicts

0x6609dc6a…a0ec

0x754704…b603

2 touches
0 conflicts

0x7a117663…cf7f

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: 0x2a68ba18…8e90c5

21 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity