Block #73,469,254

← previous blocknext block →recent activity

Analyzing

Block #73,469,254

13 transactions · 13 stateful · 2026-05-09 13:46:49 UTC

Parallelism

39/100

Blocked

54%

Avg conflicts / tx

1.69

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,469,254  ·  13 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0xa9988419…9f45

0x34b655…2a6f

2 touches
0 conflicts

0xc824469a…6425

0x34b655…2a6f

2 touches
0 conflicts

0xd563f3a1…94b1

0x34b655…2a6f

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

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